From: Stephen C. <sco...@bt...> - 2005-12-29 22:09:52
|
The code in CVS seeemed to be far from usable, so I've dived in and tried to patch it up. I've got the plugin working from within Eclipse fine, however I don't seem to be able to successfully get the plugin built. The first problem is that 50% of the tests fail when running 'maven clean plugin:install' (they all succeed when run inside Eclipse). So, has anyone else worked on getting the sf plugin running? Would you be interested in me fixing it? (scolebourne if you want to grant access). More importantly though, how do you go about solving a problem when it works in Eclipse but doesn't outside? Stephen |
From: S. <joe...@gm...> - 2005-12-29 22:44:14
|
Stephen Colebourne wrote: > The code in CVS seeemed to be far from usable, so I've dived in and > tried to patch it up. > > I've got the plugin working from within Eclipse fine, however I don't > seem to be able to successfully get the plugin built. > > The first problem is that 50% of the tests fail when running 'maven > clean plugin:install' (they all succeed when run inside Eclipse). Does it run if you don't clean before? > So, has anyone else worked on getting the sf plugin running? Would you > be interested in me fixing it? (scolebourne if you want to grant access). > > More importantly though, how do you go about solving a problem when it > works in Eclipse but doesn't outside? Most of the time you forgot, that Eclipse will automatically copy any resource from the source path into target, while you have to tell Maven explicitly, what files are resources. - Jörg |
From: Stephen C. <sco...@bt...> - 2006-01-02 23:54:25
|
Hi all, I would like to contribute my sourceforge plugin changes back. Is anyone interested in reviewing them, or giving scolebourne direct commit access? Please! Stephen Jörg Schaible wrote: > Stephen Colebourne wrote: > > >>The code in CVS seeemed to be far from usable, so I've dived in and >>tried to patch it up. >> >>I've got the plugin working from within Eclipse fine, however I don't >>seem to be able to successfully get the plugin built. >> >>The first problem is that 50% of the tests fail when running 'maven >>clean plugin:install' (they all succeed when run inside Eclipse). > > > Does it run if you don't clean before? > > >>So, has anyone else worked on getting the sf plugin running? Would you >>be interested in me fixing it? (scolebourne if you want to grant access). >> >>More importantly though, how do you go about solving a problem when it >>works in Eclipse but doesn't outside? > > > Most of the time you forgot, that Eclipse will automatically copy any > resource from the source path into target, while you have to tell Maven > explicitly, what files are resources. > > - Jörg > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
From: Eric P. <ep...@up...> - 2006-01-03 02:27:54
|
We have pretty low barrier to entry, and I know you from ASF.... =20 I've gone ahead and added you. Can't wait to see the fixes. Also, =20 I've seen Eclipse do some things with XML parsers that differ from =20 Maven.... Lastly, check out the fork mode for running junit tests... Eric On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: > Hi all, > I would like to contribute my sourceforge plugin changes back. Is =20 > anyone interested in reviewing them, or giving scolebourne direct =20 > commit access? Please! > > Stephen > > > > J=F6rg Schaible wrote: >> Stephen Colebourne wrote: >>> The code in CVS seeemed to be far from usable, so I've dived in and >>> tried to patch it up. >>> >>> I've got the plugin working from within Eclipse fine, however I =20 >>> don't >>> seem to be able to successfully get the plugin built. >>> >>> The first problem is that 50% of the tests fail when running 'maven >>> clean plugin:install' (they all succeed when run inside Eclipse). >> Does it run if you don't clean before? >>> So, has anyone else worked on getting the sf plugin running? =20 >>> Would you >>> be interested in me fixing it? (scolebourne if you want to grant =20 >>> access). >>> >>> More importantly though, how do you go about solving a problem =20 >>> when it >>> works in Eclipse but doesn't outside? >> Most of the time you forgot, that Eclipse will automatically copy any >> resource from the source path into target, while you have to tell =20 >> Maven >> explicitly, what files are resources. >> - J=F6rg >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20= >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD =20 >> SPLUNK! >> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
From: Stephen C. <sco...@bt...> - 2006-01-07 23:08:51
|
Thanks Eric. I have now checked in the (large) update, which is to most of the files in the plugin. I have verified that this works by uploading http://joda-time.sourceforge.net/contrib/jsptags v1.0 What next? Will you or someone else review it? And release it? If you want, I am happy to be granted Release Manager and Forum update capabilities so I can release it and close all the outstanding bugs/patches etc. Thanks Stephen Eric Pugh wrote: > We have pretty low barrier to entry, and I know you from ASF.... I've > gone ahead and added you. Can't wait to see the fixes. Also, I've > seen Eclipse do some things with XML parsers that differ from Maven.... > > Lastly, check out the fork mode for running junit tests... > > Eric > > On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: > >> Hi all, >> I would like to contribute my sourceforge plugin changes back. Is >> anyone interested in reviewing them, or giving scolebourne direct >> commit access? Please! >> >> Stephen >> >> >> >> Jörg Schaible wrote: >> >>> Stephen Colebourne wrote: >>> >>>> The code in CVS seeemed to be far from usable, so I've dived in and >>>> tried to patch it up. >>>> >>>> I've got the plugin working from within Eclipse fine, however I don't >>>> seem to be able to successfully get the plugin built. >>>> >>>> The first problem is that 50% of the tests fail when running 'maven >>>> clean plugin:install' (they all succeed when run inside Eclipse). >>> >>> Does it run if you don't clean before? >>> >>>> So, has anyone else worked on getting the sf plugin running? Would you >>>> be interested in me fixing it? (scolebourne if you want to grant >>>> access). >>>> >>>> More importantly though, how do you go about solving a problem when it >>>> works in Eclipse but doesn't outside? >>> >>> Most of the time you forgot, that Eclipse will automatically copy any >>> resource from the source path into target, while you have to tell Maven >>> explicitly, what files are resources. >>> - Jörg >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>> log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
From: Eric P. <ep...@up...> - 2006-01-09 15:21:29
|
Stephen, That is great... Now, in terms of releasing it, we don't use the =20 release stuff that SF provides.. INstead, we deploy into our own =20 repository, which gets synced over to ibiblio. So, go through the =20 release process like you normally would, and just deploy it into /=20 htdocs/repository/maven-plugins/... directory path. Now, are you =20 saying you can't close bugs/patches? Eric On Jan 7, 2006, at 11:08 PM, Stephen Colebourne wrote: > Thanks Eric. I have now checked in the (large) update, which is to =20 > most of the files in the plugin. > > I have verified that this works by uploading http://joda-=20 > time.sourceforge.net/contrib/jsptags v1.0 > > What next? Will you or someone else review it? And release it? > > If you want, I am happy to be granted Release Manager and Forum =20 > update capabilities so I can release it and close all the =20 > outstanding bugs/patches etc. > > Thanks > > Stephen > > > Eric Pugh wrote: >> We have pretty low barrier to entry, and I know you from =20 >> ASF.... I've gone ahead and added you. Can't wait to see the =20 >> fixes. Also, I've seen Eclipse do some things with XML parsers =20 >> that differ from Maven.... >> Lastly, check out the fork mode for running junit tests... >> Eric >> On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: >>> Hi all, >>> I would like to contribute my sourceforge plugin changes back. =20 >>> Is anyone interested in reviewing them, or giving scolebourne =20 >>> direct commit access? Please! >>> >>> Stephen >>> >>> >>> >>> J=F6rg Schaible wrote: >>> >>>> Stephen Colebourne wrote: >>>> >>>>> The code in CVS seeemed to be far from usable, so I've dived in =20= >>>>> and >>>>> tried to patch it up. >>>>> >>>>> I've got the plugin working from within Eclipse fine, however =20 >>>>> I don't >>>>> seem to be able to successfully get the plugin built. >>>>> >>>>> The first problem is that 50% of the tests fail when running =20 >>>>> 'maven >>>>> clean plugin:install' (they all succeed when run inside Eclipse). >>>> >>>> Does it run if you don't clean before? >>>> >>>>> So, has anyone else worked on getting the sf plugin running? =20 >>>>> Would you >>>>> be interested in me fixing it? (scolebourne if you want to =20 >>>>> grant access). >>>>> >>>>> More importantly though, how do you go about solving a problem =20= >>>>> when it >>>>> works in Eclipse but doesn't outside? >>>> >>>> Most of the time you forgot, that Eclipse will automatically =20 >>>> copy any >>>> resource from the source path into target, while you have to =20 >>>> tell Maven >>>> explicitly, what files are resources. >>>> - J=F6rg >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep =20 >>>> through log files >>>> for problems? Stop! Download the new AJAX search engine that =20 >>>> makes >>>> searching your log files as easy as surfing the web. DOWNLOAD =20= >>>> SPLUNK! >>>> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >>>> _______________________________________________ >>>> Maven-plugins-developer mailing list >>>> Mav...@li... >>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-=20 >>>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep =20 >>> through log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD =20 >>> SPLUNK! >>> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20= >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD =20 >> SPLUNK! >> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
From: Stephen C. <sco...@bt...> - 2006-01-10 01:24:58
|
Thanks for the help. Maven sourceforge plugin v1.3 is now released, repository updated, website refreshed etc, etc. The following is a good setup if you want to use it for maven-plugins: maven.sourceforge.project.groupId = 61626 maven.sourceforge.project.packageName = ********-plugin maven.sourceforge.publish.includes = *.jar,distributions/*-src.zip,distributions/*-src.tar.gz maven.sourceforge.publish.excludes = *-bundle.jar plus maven.sourceforge.username maven.sourceforge.password This setup will publish the src zip/gz and the jar file to SF release area. Just do 'maven dist sourceforge:deploy'. Stephen Eric Pugh wrote: > Stephen, > > That is great... Now, in terms of releasing it, we don't use the > release stuff that SF provides.. INstead, we deploy into our own > repository, which gets synced over to ibiblio. So, go through the > release process like you normally would, and just deploy it into / > htdocs/repository/maven-plugins/... directory path. Now, are you > saying you can't close bugs/patches? > > Eric > > > On Jan 7, 2006, at 11:08 PM, Stephen Colebourne wrote: > >> Thanks Eric. I have now checked in the (large) update, which is to >> most of the files in the plugin. >> >> I have verified that this works by uploading http://joda- >> time.sourceforge.net/contrib/jsptags v1.0 >> >> What next? Will you or someone else review it? And release it? >> >> If you want, I am happy to be granted Release Manager and Forum >> update capabilities so I can release it and close all the outstanding >> bugs/patches etc. >> >> Thanks >> >> Stephen >> >> >> Eric Pugh wrote: >> >>> We have pretty low barrier to entry, and I know you from ASF.... >>> I've gone ahead and added you. Can't wait to see the fixes. >>> Also, I've seen Eclipse do some things with XML parsers that differ >>> from Maven.... >>> Lastly, check out the fork mode for running junit tests... >>> Eric >>> On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: >>> >>>> Hi all, >>>> I would like to contribute my sourceforge plugin changes back. Is >>>> anyone interested in reviewing them, or giving scolebourne direct >>>> commit access? Please! >>>> >>>> Stephen >>>> >>>> >>>> >>>> Jörg Schaible wrote: >>>> >>>>> Stephen Colebourne wrote: >>>>> >>>>>> The code in CVS seeemed to be far from usable, so I've dived in and >>>>>> tried to patch it up. >>>>>> >>>>>> I've got the plugin working from within Eclipse fine, however I >>>>>> don't >>>>>> seem to be able to successfully get the plugin built. >>>>>> >>>>>> The first problem is that 50% of the tests fail when running 'maven >>>>>> clean plugin:install' (they all succeed when run inside Eclipse). >>>>> >>>>> >>>>> Does it run if you don't clean before? >>>>> >>>>>> So, has anyone else worked on getting the sf plugin running? >>>>>> Would you >>>>>> be interested in me fixing it? (scolebourne if you want to grant >>>>>> access). >>>>>> >>>>>> More importantly though, how do you go about solving a problem >>>>>> when it >>>>>> works in Eclipse but doesn't outside? >>>>> >>>>> >>>>> Most of the time you forgot, that Eclipse will automatically copy any >>>>> resource from the source path into target, while you have to tell >>>>> Maven >>>>> explicitly, what files are resources. >>>>> - Jörg >>>>> ------------------------------------------------------- >>>>> This SF.net email is sponsored by: Splunk Inc. Do you grep >>>>> through log files >>>>> for problems? Stop! Download the new AJAX search engine that makes >>>>> searching your log files as easy as surfing the web. DOWNLOAD >>>>> SPLUNK! >>>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>>>> _______________________________________________ >>>>> Maven-plugins-developer mailing list >>>>> Mav...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins- developer >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>>> log files >>>> for problems? Stop! Download the new AJAX search engine that makes >>>> searching your log files as easy as surfing the web. DOWNLOAD >>>> SPLUNK! >>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>>> _______________________________________________ >>>> Maven-plugins-developer mailing list >>>> Mav...@li... >>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>> log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >>> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |