[jira] Commented: (MAVENUPLOAD-797) Add sources to commons-validator 1.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-797?page=comments#action_62144 ] Grzegorz Slowikowski commented on MAVENUPLOAD-797: -- I think the sources jar in your boundle is not valid. It should contain only java sources (commons-validator-1.3.0-src/src/share directory in this exapmle). It would be best if it was generated by maven (sources:jar). By the way, what can we do to have sources and javadoc jars for artifacts converted from Maven1. > Add sources to commons-validator 1.3.0 > -- > > Key: MAVENUPLOAD-797 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-797 > Project: maven-upload-requests > Type: Improvement > Reporter: Tomislav Stojcevich > Attachments: commons-validator-1.3.0-bundle.jar > > > Add sources only from bundle to commons-validator 1.3.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-545) allow xmlrpc access to build results log
[ http://jira.codehaus.org/browse/CONTINUUM-545?page=all ] Emmanuel Venisse closed CONTINUUM-545: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0.3 > allow xmlrpc access to build results log > > > Key: CONTINUUM-545 > URL: http://jira.codehaus.org/browse/CONTINUUM-545 > Project: Continuum > Type: New Feature > Components: XMLRPC Interface > Reporter: Milos Kleint > Assignee: Emmanuel Venisse > Priority: Critical > Fix For: 1.0.3 > > > currently the xmlrpc access cannot read build results, it's not included for > performance reasons. But without means of accessing it, the netbeans > integration is just half as useful. Providing an URL on the server for the > build should be enough. > irc log: > another Q: will it be possible to get the build results/output from rpc? > currently I didn't figure how.. > evenissemethod is missing in rpc server > trygvis yeah, that was deliberate > evenisseyou can add it > DefaultContinum.getBuildResult(id).getOutput() > trygvis we should make a special servlet for returning the build output > evenissewhy? due to output length? > trygvis yep > trygvis useful for the web UI anyway > trygvis I'm afraid that giving the xml-rpc stuff 20MB of logs will give > a OutOfMemoryException > evenisse20MB for an build output, pff > trygvis hehe, the geronimo build is at least that! > evenisseok, so mkleint, don't use rpc for output ;-) > mkleint can have at least the ending portion of the output log? > mkleint evenisse: kind of sucks, the IDE integration not usefule much > then.. I assumed it will be added someday.. > mkleint or produce an URL that can be opened on request.. > trygvis you can do a simple HTTP GET to get it > trygvis right :) > mkleint how to construct the URL? > trygvis it's not implemented, but probably root>/build-output/ > mkleint btw I'm also not getting the list of builds in rpc at all.. a > bug or not implemented either? > evenissewith 1.0.* > http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID > evenisseand get on it only what you need > <--|jsisson has left #continuum (jsisson) > trygvis won't that give you an entire html page= > trygvis ? > evenisseyes :) > evenissebut output is after "Output" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-85) Maven eclipse plugin generates duplicate entries in .project file
[ http://jira.codehaus.org/browse/MECLIPSE-85?page=comments#action_62143 ] Geoffrey De Smet commented on MECLIPSE-85: -- I was unsure it was the same issue as ours, so I posted a new one describing ours in detail: http://jira.codehaus.org/browse/MECLIPSE-86 They might have the same cause. > Maven eclipse plugin generates duplicate entries in .project file > - > > Key: MECLIPSE-85 > URL: http://jira.codehaus.org/browse/MECLIPSE-85 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.1 > Reporter: Shashikala Shamarao > > > Hi, > I have written a pom.xml for my project which has lot of sub-modules and each > of these modules contain pom.xml file. > main project > - arch project > - servs project (this project is an ejb module) > - client project > In the main pom.file, I have defined the dependency for these other modules. > When I generate .project and .classpath file, it puts duplicate entry for the > ejb modules due to which when I load them into eclipse, it does not build > properly. > Can anyone help me with this. > Thanks in advance, > Shashi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSUREFIREREP-17) Use javascript to show/hide failure details
[ http://jira.codehaus.org/browse/MSUREFIREREP-17?page=all ] Carlos Sanchez updated MSUREFIREREP-17: --- Fix Version: 2.0 > Use javascript to show/hide failure details > --- > > Key: MSUREFIREREP-17 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-17 > Project: Maven 2.x Surefire report Plugin > Type: Improvement > Reporter: Carlos Sanchez > Priority: Minor > Fix For: 2.0 > Attachments: javascript.diff > > > From MSUREFIREREP-15, patch for just the javascript addition -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-86) Dependencies of type test-jar get added twice
Dependencies of type test-jar get added twice
-
Key: MECLIPSE-86
URL: http://jira.codehaus.org/browse/MECLIPSE-86
Project: Maven 2.x Eclipse Plugin
Type: Bug
Versions: 2.1
Reporter: Geoffrey De Smet
Fix For: 2.2
Consider a project with these dependencies:
org.springframework.richclient
spring-richclient-core
${pom.version}
org.springframework.richclient
spring-richclient-core
test-jar
${pom.version}
test
>From Larry Streepy:
"When the eclipse plugin processes this pom, it processes both dependency
entries and adds each of them to the classpath as type "src". It
doesn't appear to be doing any kind of handling for duplicate entries,
and I see nothing in the plugin code that seems to deal with the "type"
of a dependency."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-85) Maven eclipse plugin generates duplicate entries in .project file
[ http://jira.codehaus.org/browse/MECLIPSE-85?page=comments#action_62142 ]
Geoffrey De Smet commented on MECLIPSE-85:
--
We 've seen this problem when depending on test-jars:
org.springframework.richclient
spring-richclient-core
${pom.version}
org.springframework.richclient
spring-richclient-core
test-jar
${pom.version}
test
> Maven eclipse plugin generates duplicate entries in .project file
> -
>
> Key: MECLIPSE-85
> URL: http://jira.codehaus.org/browse/MECLIPSE-85
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.1
> Reporter: Shashikala Shamarao
>
>
> Hi,
> I have written a pom.xml for my project which has lot of sub-modules and each
> of these modules contain pom.xml file.
> main project
> - arch project
> - servs project (this project is an ejb module)
> - client project
> In the main pom.file, I have defined the dependency for these other modules.
> When I generate .project and .classpath file, it puts duplicate entry for the
> ejb modules due to which when I load them into eclipse, it does not build
> properly.
> Can anyone help me with this.
> Thanks in advance,
> Shashi
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-19) Separate report generation & database generation
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_62141 ] Vincent Massol commented on MCLOVER-19: --- FWIW, here is what I'm currently working on: * Create a clover:report mojo that does not fork a lifecycle and simply generate a report out of a clover database * Expose clover:instrument (which is currently an internal mojo). * Modify the clover:clover mojo to support aggregating clover databases when run as part of a multimodule build in order to generate a single all-encompassing clover report > Separate report generation & database generation > > > Key: MCLOVER-19 > URL: http://jira.codehaus.org/browse/MCLOVER-19 > Project: Maven 2.x Clover Plugin > Type: Improvement > Versions: 2.0 > Reporter: Mike Perham > Assignee: Vincent Massol > Fix For: 2.1 > > > From my email to the user list: > How do we get the Clover report to generate as part of the normal build? > If I run 'mvn clover:clover' it generates the report but does not perform the > install process. > If I run 'mvn site:site' with the clover report plugin, same as clover:clover. > If I run 'mvn install site:site', it builds the project twice. > Is there a way to get the clover database generated from the normal build > lifecycle and the site report to use that pre-generated database so it does > not have to build twice? My projects cannot build twice in a row - they > assume a clean build every time. The HowTo does not cover this usecase but > it seems pretty common to want the daily build to create the artifacts AND > document the status of your unit tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPDIST-21) additional type of source distribution
[ http://jira.codehaus.org/browse/MPDIST-21?page=all ] Lukas Theussl closed MPDIST-21: --- Resolution: Won't Fix This functionality is now provided by the source plugin. > additional type of source distribution > --- > > Key: MPDIST-21 > URL: http://jira.codehaus.org/browse/MPDIST-21 > Project: maven-dist-plugin > Type: New Feature > Reporter: Milos Kleint > Attachments: maven-dist.patch > > > It would be valuable to have additional type of source distribution, a source > jar that has the same structure as the jar and javadoc jar. It's useful for > use in IDEs for debugging, examining source for dependencies etc. If such > source distributions get uploaded to remote servers along with the jars and > javadoc jars, it's fairly easy to automate the download and use in the IDE > for any dependency of the currently used project. (I would like to use this > feature in mevenide) > The proposed patch is attached. If you accept the patch, I can also try to > write the docs for the feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCLOVER-22) The licenseFile element is not taken into account
[ http://jira.codehaus.org/browse/MCLOVER-22?page=all ] Vincent Massol closed MCLOVER-22: - Resolution: Won't Fix It's now documented in the Clover plugin site. > The licenseFile element is not taken into account > - > > Key: MCLOVER-22 > URL: http://jira.codehaus.org/browse/MCLOVER-22 > Project: Maven 2.x Clover Plugin > Type: Bug > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > > > The licenseFile appears not to be used by the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCLOVER-24) Configure Clover to skip certain files when doing coverage calculation
[ http://jira.codehaus.org/browse/MCLOVER-24?page=all ] Vincent Massol updated MCLOVER-24: -- Version: (was: 2.0-alpha-1) (was: 2.1) Fix Version: (was: 2.1) (was: 2.0) (was: 2.0-alpha-1) > Configure Clover to skip certain files when doing coverage calculation > -- > > Key: MCLOVER-24 > URL: http://jira.codehaus.org/browse/MCLOVER-24 > Project: Maven 2.x Clover Plugin > Type: New Feature > Versions: 2.0 > Environment: all > Reporter: Christian Cabanero > > > It would be really nice to be able to configure clover so that it would > exclude certain files as part of its test decoration and it's code coverage > statistics. It be nice to be able to specify these through ant-style > filesets or something similar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-38) Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn eclipse:eclipse succeeds)
[ http://jira.codehaus.org/browse/SUREFIRE-38?page=comments#action_62138 ] Carlos Sanchez commented on SUREFIRE-38: Can your try setting childDelegation to false in your surefire plugin configuration? > Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn > eclipse:eclipse succeeds) > > > Key: SUREFIRE-38 > URL: http://jira.codehaus.org/browse/SUREFIRE-38 > Project: surefire > Type: Bug > Versions: 1.5.2 > Environment: maven 2.0.3 > Reporter: Dan Greening > Assignee: Jason van Zyl > Priority: Critical > Attachments: jboss-ejb3-embeddable-test-with-junit.tar.gz > > > JBoss's EJB3 embeddable container, which is very handy for unit testing EJB's > without using an application server, will not work under surefire in Maven2. > It works fine under Maven1. Furthermore, it ALSO works using the Maven2 > eclipse-plugin generated .project/.classpath in Eclipse. > Here's a complete set of instruction to reproduce it. > This is a test showing that surefire does not properly handle the JBoss EJB3 > embeddable container. > The instructions are a bit complex, because you have to download a package of > JARs from JBoss. (They make the test file too big to attach in JIRA.) > To confirm, > 1. cd /tmp > 2. Surf to > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=132063 > 3. Download jboss-EJB-3.0_Embeddable_ALPHA_5.zip. Put it in /tmp. This is >the latest EJB3 embeddable system. > 4. unzip jboss-EJB-3.0_Embeddable_ALPHA_5.zip > 5. Download jboss-ejb3-embeddable-test-with-junit.tar.gz (it is an attachment >to this JIRA ticket). > 6. tar xvfz jboss-ejb3-embeddable-test-with-junit.tar.gz > 7. cd jboss-ejb3-embeddable-test-with-junit > 8. cp -pR ../jboss-EJB-3.0_Embeddable_ALPHA_5/lib lib > 9. ./deploy-jars.perl > 10. type "mvn test". > 11. Note that the test fails. > 12. Type "mvn eclipse:eclipse" > 13. Import the jboss-ejb3-embeddable-test-with-junit directory into Eclipse > as an "existing project". > 14. Set M2_REPO build variable to your .m2/repository folder. > 15. Run the EmbeddedEjb3TestCase as a JUnit test in Eclipse. It works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSOURCES-2) Maven Sources Plugin should be able to distribute test sources as well as main sources
[ http://jira.codehaus.org/browse/MSOURCES-2?page=comments#action_62136 ] Edwin Punzalan commented on MSOURCES-2: --- To make it consistent with the jar plugin, i renamed the goal to source:test-jar > Maven Sources Plugin should be able to distribute test sources as well as > main sources > -- > > Key: MSOURCES-2 > URL: http://jira.codehaus.org/browse/MSOURCES-2 > Project: Maven 2.x Sources Plugin > Type: Improvement > Environment: all > Reporter: Dan Fabulich > Assignee: Maria Odea Ching > Fix For: 2.0.1 > Attachments: MSOURCES-2-maven-source-plugin.patch, > MSOURCES-2-maven-source-plugin.patch > > Original Estimate: 5 hours >Time Spent: 4 hours, 15 minutes > Remaining: 45 minutes > > The Maven Sources Plugin doesn't appear to have a way to distribute the test > sources along with the actual product sources. Since automated tests can > serve as good examples/working documentation, it would be nice to be able to > distribute these in my build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSOURCES-2) Maven Sources Plugin should be able to distribute test sources as well as main sources
[ http://jira.codehaus.org/browse/MSOURCES-2?page=all ] Edwin Punzalan closed MSOURCES-2: - Resolution: Fixed Patch applied. Thanks. > Maven Sources Plugin should be able to distribute test sources as well as > main sources > -- > > Key: MSOURCES-2 > URL: http://jira.codehaus.org/browse/MSOURCES-2 > Project: Maven 2.x Sources Plugin > Type: Improvement > Environment: all > Reporter: Dan Fabulich > Assignee: Maria Odea Ching > Fix For: 2.0.1 > Attachments: MSOURCES-2-maven-source-plugin.patch, > MSOURCES-2-maven-source-plugin.patch > > Original Estimate: 5 hours >Time Spent: 4 hours, 15 minutes > Remaining: 45 minutes > > The Maven Sources Plugin doesn't appear to have a way to distribute the test > sources along with the actual product sources. Since automated tests can > serve as good examples/working documentation, it would be nice to be able to > distribute these in my build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2180) Allow aggregation mojos to access plugin configurations
[ http://jira.codehaus.org/browse/MNG-2180?page=comments#action_62134 ] Milos Kleint commented on MNG-2180: --- another usecase is the IDE integration where I need to check the location of generated sources for example. or I need to figure out the version of the javac that is used by the compiler plugin..etc.. > Allow aggregation mojos to access plugin configurations > --- > > Key: MNG-2180 > URL: http://jira.codehaus.org/browse/MNG-2180 > Project: Maven 2 > Type: Improvement > Components: Plugin API > Versions: 2.0.3 > Reporter: Vincent Massol > > > Here's my use case: > * I'm writing an aggregated report for the clover plugin. It needs to locate > all children's clover databases and merge them into a single one and then > generate a report out of it > * The location of the Clover databases is stored in plugin's configuration > * The problem is that I cannot access a plugin configuration using the plugin > API > This is a general problem. By definition any aggregation mojo needs to access > configuration information from its children. Some time out of sheer luck the > information the plugin needs is found in the general section of the POM. > However this is very limited and forbids any use case where the configuration > is stored in . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-38) Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn eclipse:eclipse succeeds)
Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn eclipse:eclipse succeeds) Key: SUREFIRE-38 URL: http://jira.codehaus.org/browse/SUREFIRE-38 Project: surefire Type: Bug Versions: 1.5.2 Environment: maven 2.0.3 Reporter: Dan Greening Assigned to: Jason van Zyl Priority: Critical Attachments: jboss-ejb3-embeddable-test-with-junit.tar.gz JBoss's EJB3 embeddable container, which is very handy for unit testing EJB's without using an application server, will not work under surefire in Maven2. It works fine under Maven1. Furthermore, it ALSO works using the Maven2 eclipse-plugin generated .project/.classpath in Eclipse. Here's a complete set of instruction to reproduce it. This is a test showing that surefire does not properly handle the JBoss EJB3 embeddable container. The instructions are a bit complex, because you have to download a package of JARs from JBoss. (They make the test file too big to attach in JIRA.) To confirm, 1. cd /tmp 2. Surf to http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=132063 3. Download jboss-EJB-3.0_Embeddable_ALPHA_5.zip. Put it in /tmp. This is the latest EJB3 embeddable system. 4. unzip jboss-EJB-3.0_Embeddable_ALPHA_5.zip 5. Download jboss-ejb3-embeddable-test-with-junit.tar.gz (it is an attachment to this JIRA ticket). 6. tar xvfz jboss-ejb3-embeddable-test-with-junit.tar.gz 7. cd jboss-ejb3-embeddable-test-with-junit 8. cp -pR ../jboss-EJB-3.0_Embeddable_ALPHA_5/lib lib 9. ./deploy-jars.perl 10. type "mvn test". 11. Note that the test fails. 12. Type "mvn eclipse:eclipse" 13. Import the jboss-ejb3-embeddable-test-with-junit directory into Eclipse as an "existing project". 14. Set M2_REPO build variable to your .m2/repository folder. 15. Run the EmbeddedEjb3TestCase as a JUnit test in Eclipse. It works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-2) Maven Sources Plugin should be able to distribute test sources as well as main sources
[ http://jira.codehaus.org/browse/MSOURCES-2?page=all ] Maria Odea Ching updated MSOURCES-2: Attachment: MSOURCES-2-maven-source-plugin.patch > Maven Sources Plugin should be able to distribute test sources as well as > main sources > -- > > Key: MSOURCES-2 > URL: http://jira.codehaus.org/browse/MSOURCES-2 > Project: Maven 2.x Sources Plugin > Type: Improvement > Environment: all > Reporter: Dan Fabulich > Assignee: Maria Odea Ching > Fix For: 2.0.1 > Attachments: MSOURCES-2-maven-source-plugin.patch, > MSOURCES-2-maven-source-plugin.patch > > Original Estimate: 5 hours >Time Spent: 4 hours, 15 minutes > Remaining: 45 minutes > > The Maven Sources Plugin doesn't appear to have a way to distribute the test > sources along with the actual product sources. Since automated tests can > serve as good examples/working documentation, it would be nice to be able to > distribute these in my build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSUREFIREREP-1) Report sould link to Sources (jxr-plugin)
[ http://jira.codehaus.org/browse/MSUREFIREREP-1?page=all ] Allan Ramirez closed MSUREFIREREP-1: Resolution: Fixed Fix Version: (was: 2.0) Fixed in SVN. Link to the sources will only be available if maven-jxr-plugin is declared in the reporting section. > Report sould link to Sources (jxr-plugin) > - > > Key: MSUREFIREREP-1 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-1 > Project: Maven 2.x Surefire report Plugin > Type: Improvement > Reporter: Fabian Bauschulte > Assignee: Allan Ramirez > > Original Estimate: 8 hours > Remaining: 8 hours > > Like for example the pmd-plugin the Surefire report could provide a link from > the tested method / error line to the relevant sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGELOG-17) changelog, file activity and developer activity reports are all identical (to the changelog report)
changelog, file activity and developer activity reports are all identical (to the changelog report) --- Key: MCHANGELOG-17 URL: http://jira.codehaus.org/browse/MCHANGELOG-17 Project: Maven 2.x Changelog Plugin Type: Bug Versions: 2.0 Environment: osx 10.4.5, java 1.4.2_09 Reporter: Julian Wood Given this part of the pom, I get links to 3 reports in the site, but all are just the changelog report in duplicate. I tested this before (and after) applying the MCHANGELOG-16.patch, but after the MCHANGELOG-15.patch, which is required to get the report to run without exceptions, so this would seem to have something to do with the move from mojo to maven code trees. org.apache.maven.plugins maven-changelog-plugin 2.0-beta-2-SNAPSHOT changes http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= range 90 changelog file-activity dev-activity -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-15) String index out of range error
[ http://jira.codehaus.org/browse/MCHANGELOG-15?page=comments#action_62127
]
Julian Wood commented on MCHANGELOG-15:
---
The patch in MCHANGELOG-16 includes this patch, so I imagine we should skip
this patch. Sorry for the dupe.
> String index out of range error
> ---
>
> Key: MCHANGELOG-15
> URL: http://jira.codehaus.org/browse/MCHANGELOG-15
> Project: Maven 2.x Changelog Plugin
> Type: Bug
> Versions: 2.0
> Environment: osx 10.4.5, java 1.4.2_09
> Reporter: Julian Wood
> Priority: Critical
> Attachments: MCHANGELOG-15.patch
>
>
> Here's the relevant parts of my pom:
>
> scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
>
> scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
>
> http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk
>
>
> org.apache.maven.plugins
> maven-changelog-plugin
> 2.0-beta-2-SNAPSHOT
>
>
> changes
>
>
> http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&path=
> range
> 60
>
>
> changelog
> file-activity
> dev-activity
>
>
>
>
> I get this error when trying to build my site:
> [INFO] Executing: svn --non-interactive log -v -r "{2006-01-26 21:20:36
> +}:{2006-03-28 21:20:36 +}"
> http://apollo.ucalgary.ca:8800/pmgt/trunk/pmgt-webapp
> [INFO] Working directory:
> /Users/woodj/Documents/pmgt/pmgt/trunk/pmgt-webapp/src/main/java
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at java.lang.String.substring(String.java:1735)
> at
> org.apache.maven.changelog.ChangeLogReport.initReportUrls(ChangeLogReport.java:973)
> at
> org.apache.maven.changelog.ChangeLogReport.doChangedSetDetail(ChangeLogReport.java:934)
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Julian Wood updated MCHANGELOG-16: -- Attachment: test.zip > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 > Reporter: Julian Wood > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Julian Wood updated MCHANGELOG-16: -- Attachment: MCHANGELOG-16.patch > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 > Reporter: Julian Wood > Attachments: MCHANGELOG-16.patch > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGELOG-16) when using svn, links are wrong
when using svn, links are wrong --- Key: MCHANGELOG-16 URL: http://jira.codehaus.org/browse/MCHANGELOG-16 Project: Maven 2.x Changelog Plugin Type: Bug Versions: 2.0 Environment: osx 10.4.5, java 1.4.2_09 Reporter: Julian Wood Here's my setup: scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk ... org.apache.maven.plugins maven-changelog-plugin 2.0-beta-2-SNAPSHOT changes http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= range 90 changelog file-activity dev-activity With that displayFileDetailUrl, I get links like this in the resultant changelog in my site: http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= but it should be like this: link = http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-85) Maven eclipse plugin generates duplicate entries in .project file
Maven eclipse plugin generates duplicate entries in .project file - Key: MECLIPSE-85 URL: http://jira.codehaus.org/browse/MECLIPSE-85 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.1 Reporter: Shashikala Shamarao Hi, I have written a pom.xml for my project which has lot of sub-modules and each of these modules contain pom.xml file. main project - arch project - servs project (this project is an ejb module) - client project In the main pom.file, I have defined the dependency for these other modules. When I generate .project and .classpath file, it puts duplicate entry for the ejb modules due to which when I load them into eclipse, it does not build properly. Can anyone help me with this. Thanks in advance, Shashi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSUREFIREREP-15) Add integration logic that allows report to be created for junit OR testng
[ http://jira.codehaus.org/browse/MSUREFIREREP-15?page=all ] Carlos Sanchez updated MSUREFIREREP-15: --- Attachment: testngjunit.diff > Add integration logic that allows report to be created for junit OR testng > -- > > Key: MSUREFIREREP-15 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-15 > Project: Maven 2.x Surefire report Plugin > Type: Improvement > Environment: any > Reporter: Jesse Kuhnert > Fix For: 2.0 > Attachments: maven-surefire-report-maven-plugin-patch.txt, testngjunit.diff > > > I'm currently in the middle of patching/working with testng and the > maven-surefire plugin core parts to provide a seamless testng integration > point and am on the final task of getting the report to be a little > friendlier. This is the jira issue for the surefire portion: > http://jira.codehaus.org/browse/MSUREFIRE-23 > I think at the very least I wanted to change the runtime to ~not~ try and > parse class/package constructs out of the test name attributes, but work in > an agnostic manner to just group things as they appear in the xml output. I > also intend to embed a very minimal amount of javascript into the generated > html page so that report errors/stack traces can have hide/show buttons > enabling the detailed viewing of their contents. > Does this sound reasonable to everyone? I've got the source checked out right > now and will be working on this today. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSUREFIREREP-17) Use javascript to show/hide failure details
Use javascript to show/hide failure details --- Key: MSUREFIREREP-17 URL: http://jira.codehaus.org/browse/MSUREFIREREP-17 Project: Maven 2.x Surefire report Plugin Type: Improvement Reporter: Carlos Sanchez Priority: Minor Attachments: javascript.diff >From MSUREFIREREP-15, patch for just the javascript addition -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSUREFIREREP-15) Add integration logic that allows report to be created for junit OR testng
[ http://jira.codehaus.org/browse/MSUREFIREREP-15?page=comments#action_62118 ] Allan Ramirez commented on MSUREFIREREP-15: --- Hi Jesse, how is the patch? > Add integration logic that allows report to be created for junit OR testng > -- > > Key: MSUREFIREREP-15 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-15 > Project: Maven 2.x Surefire report Plugin > Type: Improvement > Environment: any > Reporter: Jesse Kuhnert > Fix For: 2.0 > Attachments: maven-surefire-report-maven-plugin-patch.txt > > > I'm currently in the middle of patching/working with testng and the > maven-surefire plugin core parts to provide a seamless testng integration > point and am on the final task of getting the report to be a little > friendlier. This is the jira issue for the surefire portion: > http://jira.codehaus.org/browse/MSUREFIRE-23 > I think at the very least I wanted to change the runtime to ~not~ try and > parse class/package constructs out of the test name attributes, but work in > an agnostic manner to just group things as they appear in the xml output. I > also intend to embed a very minimal amount of javascript into the generated > html page so that report errors/stack traces can have hide/show buttons > enabling the detailed viewing of their contents. > Does this sound reasonable to everyone? I've got the source checked out right > now and will be working on this today. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MSOURCES-2) Maven Sources Plugin should be able to distribute test sources as well as main sources
[ http://jira.codehaus.org/browse/MSOURCES-2?page=all ] Maria Odea Ching reopened MSOURCES-2: - Add separate goal for creating test sources jar instead of using the includeTestSources parameter. > Maven Sources Plugin should be able to distribute test sources as well as > main sources > -- > > Key: MSOURCES-2 > URL: http://jira.codehaus.org/browse/MSOURCES-2 > Project: Maven 2.x Sources Plugin > Type: Improvement > Environment: all > Reporter: Dan Fabulich > Assignee: Maria Odea Ching > Fix For: 2.0.1 > Attachments: MSOURCES-2-maven-source-plugin.patch > > Original Estimate: 5 hours >Time Spent: 4 hours, 15 minutes > Remaining: 45 minutes > > The Maven Sources Plugin doesn't appear to have a way to distribute the test > sources along with the actual product sources. Since automated tests can > serve as good examples/working documentation, it would be nice to be able to > distribute these in my build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGELOG-14) Build fails because cvslib dependency has moved.
[ http://jira.codehaus.org/browse/MCHANGELOG-14?page=all ] Edwin Punzalan closed MCHANGELOG-14: Assign To: Edwin Punzalan Resolution: Fixed Removed unnecessary deps from the plugin pom. SVN rev 389335 > Build fails because cvslib dependency has moved. > > > Key: MCHANGELOG-14 > URL: http://jira.codehaus.org/browse/MCHANGELOG-14 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > > > The netbeans:cvslib:3.6 dependency is now outdated and points to a new > dependency: org.netbeans:lib:3.6, however only the pom exists in maven > central, so the build fails with an artifact not found error. > I had to install it manually before changelog would build. This is really a > problem with org.netbeans:lib:3.6, but since it affects changelog, I am > reporting the issue here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSOURCES-2) Maven Sources Plugin should be able to distribute test sources as well as main sources
[ http://jira.codehaus.org/browse/MSOURCES-2?page=comments#action_62115 ] Maria Odea Ching commented on MSOURCES-2: - Yeah, I agree with you. I think it would be a better design. Anyway, I'll make the necessary changes in the code and submit another patch. Thanks for the input :) > Maven Sources Plugin should be able to distribute test sources as well as > main sources > -- > > Key: MSOURCES-2 > URL: http://jira.codehaus.org/browse/MSOURCES-2 > Project: Maven 2.x Sources Plugin > Type: Improvement > Environment: all > Reporter: Dan Fabulich > Assignee: Maria Odea Ching > Fix For: 2.0.1 > Attachments: MSOURCES-2-maven-source-plugin.patch > > Original Estimate: 5 hours >Time Spent: 4 hours, 15 minutes > Remaining: 45 minutes > > The Maven Sources Plugin doesn't appear to have a way to distribute the test > sources along with the actual product sources. Since automated tests can > serve as good examples/working documentation, it would be nice to be able to > distribute these in my build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-31) Create a tool that will generate an archetype from an existing project
[ http://jira.codehaus.org/browse/ARCHETYPE-31?page=comments#action_62114 ] Jason van Zyl commented on ARCHETYPE-31: This is working but it needs a lot of testing and won't coincide with the 2.0.3 release. It has its own lifecycle so when it's ready you won't have to wait for a release of Maven core. > Create a tool that will generate an archetype from an existing project > -- > > Key: ARCHETYPE-31 > URL: http://jira.codehaus.org/browse/ARCHETYPE-31 > Project: Maven Archetype > Type: New Feature > Reporter: Jason van Zyl > Assignee: Jason van Zyl > Fix For: 0.7 > > > An archetype author shold be able to work/debug an existing project and when > satisfied just flip it into an archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSUREFIRE-84) JUnit 4 integration
JUnit 4 integration --- Key: MSUREFIRE-84 URL: http://jira.codehaus.org/browse/MSUREFIRE-84 Project: Maven 2.x Surefire Plugin Type: Wish Reporter: Shinobu Kawai Yoshida Priority: Minor It would be great if we could integrate surefire plugin with JUnit 4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANT-9) Ant task documentation dependency link is broken
Ant task documentation dependency link is broken Key: MANT-9 URL: http://jira.codehaus.org/browse/MANT-9 Project: Maven 2.x Ant Plugin Type: Bug Environment: maven website Reporter: Rick Mann Priority: Minor On this page: http://maven.apache.org/ant-tasks.html If you scroll down to "Getting Help", and click "Dependency Mechanism", you are incorrectly sent to the following page: http://maven.apache.org/dependencies.html This page lists build dependencies for Maven, not documentation about the dependency mechanism. I don't know where the correct page is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGELOG-15) String index out of range error
[ http://jira.codehaus.org/browse/MCHANGELOG-15?page=all ]
Julian Wood updated MCHANGELOG-15:
--
Attachment: MCHANGELOG-15.patch
> String index out of range error
> ---
>
> Key: MCHANGELOG-15
> URL: http://jira.codehaus.org/browse/MCHANGELOG-15
> Project: Maven 2.x Changelog Plugin
> Type: Bug
> Versions: 2.0
> Environment: osx 10.4.5, java 1.4.2_09
> Reporter: Julian Wood
> Priority: Critical
> Attachments: MCHANGELOG-15.patch
>
>
> Here's the relevant parts of my pom:
>
> scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
>
> scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
>
> http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk
>
>
> org.apache.maven.plugins
> maven-changelog-plugin
> 2.0-beta-2-SNAPSHOT
>
>
> changes
>
>
> http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&path=
> range
> 60
>
>
> changelog
> file-activity
> dev-activity
>
>
>
>
> I get this error when trying to build my site:
> [INFO] Executing: svn --non-interactive log -v -r "{2006-01-26 21:20:36
> +}:{2006-03-28 21:20:36 +}"
> http://apollo.ucalgary.ca:8800/pmgt/trunk/pmgt-webapp
> [INFO] Working directory:
> /Users/woodj/Documents/pmgt/pmgt/trunk/pmgt-webapp/src/main/java
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1768)
> at java.lang.String.substring(String.java:1735)
> at
> org.apache.maven.changelog.ChangeLogReport.initReportUrls(ChangeLogReport.java:973)
> at
> org.apache.maven.changelog.ChangeLogReport.doChangedSetDetail(ChangeLogReport.java:934)
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (MCHANGELOG-15) String index out of range error
String index out of range error
---
Key: MCHANGELOG-15
URL: http://jira.codehaus.org/browse/MCHANGELOG-15
Project: Maven 2.x Changelog Plugin
Type: Bug
Versions: 2.0
Environment: osx 10.4.5, java 1.4.2_09
Reporter: Julian Wood
Priority: Critical
Here's the relevant parts of my pom:
scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk
http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk
org.apache.maven.plugins
maven-changelog-plugin
2.0-beta-2-SNAPSHOT
changes
http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&path=
range
60
changelog
file-activity
dev-activity
I get this error when trying to build my site:
[INFO] Executing: svn --non-interactive log -v -r "{2006-01-26 21:20:36
+}:{2006-03-28 21:20:36 +}"
http://apollo.ucalgary.ca:8800/pmgt/trunk/pmgt-webapp
[INFO] Working directory:
/Users/woodj/Documents/pmgt/pmgt/trunk/pmgt-webapp/src/main/java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] String index out of range: -1
[INFO]
[INFO] Trace
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1768)
at java.lang.String.substring(String.java:1735)
at
org.apache.maven.changelog.ChangeLogReport.initReportUrls(ChangeLogReport.java:973)
at
org.apache.maven.changelog.ChangeLogReport.doChangedSetDetail(ChangeLogReport.java:934)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (MCHANGELOG-14) Build fails because cvslib dependency has moved.
Build fails because cvslib dependency has moved. Key: MCHANGELOG-14 URL: http://jira.codehaus.org/browse/MCHANGELOG-14 Project: Maven 2.x Changelog Plugin Type: Bug Versions: 2.0 Environment: osx 10.4.5, java 1.4.2_09 Reporter: Julian Wood Priority: Minor The netbeans:cvslib:3.6 dependency is now outdated and points to a new dependency: org.netbeans:lib:3.6, however only the pom exists in maven central, so the build fails with an artifact not found error. I had to install it manually before changelog would build. This is really a problem with org.netbeans:lib:3.6, but since it affects changelog, I am reporting the issue here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-168) PerforceChangeLogConsumer should use relative paths
[ http://jira.codehaus.org/browse/SCM-168?page=all ]
Mike Perham closed SCM-168:
---
Resolution: Fixed
Fix Version: 1.0
> PerforceChangeLogConsumer should use relative paths
> ---
>
> Key: SCM-168
> URL: http://jira.codehaus.org/browse/SCM-168
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-perforce
> Versions: 1.0
> Reporter: John Didion
> Assignee: Mike Perham
> Priority: Critical
> Fix For: 1.0
> Attachments: PerforceChangeLogConsumer.diff
>
>
> It seems like all scm providers are dealing with relative paths, rather than
> absolute repository paths. PerforceCheckOutCommand is definitely doing this.
> PerforceChangeLogConsumer, however, does not, which means
> ChangeSet.containsFilename always returns false because it's comparing a
> relative path to an absolute one.
> There are two changes. First, in PerforceChangeLogCommand:
> {noformat}
> PerforceChangeLogConsumer consumer = new PerforceChangeLogConsumer(
> ((PerforceScmProviderRepository) repo).getPath(), startDate, endDate );
> {noformat}
> The attached diff is for the second set of changes, which are to
> PerforceChangeLogConsumer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=all ] Mike Perham closed SCM-165: --- Resolution: Fixed Fix Version: 1.0 > PerforceChangeLogCommand needs to use the same clientspec as the update > command > --- > > Key: SCM-165 > URL: http://jira.codehaus.org/browse/SCM-165 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0 > Reporter: John Didion > Assignee: Mike Perham > Priority: Critical > Fix For: 1.0 > Attachments: PerforceChangeLogCommand.diff, svn.diff > > > The PerforceChangeLogCommand as written does not work if the update was done > with the client spec generated by the checkout/update command. The attached > diff will fix the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-31) Create a tool that will generate an archetype from an existing project
[ http://jira.codehaus.org/browse/ARCHETYPE-31?page=comments#action_62109 ] Matt Raible commented on ARCHETYPE-31: -- Jason - you mentioned you had this completed at TSSJS last week. Is it scheduled to go into an upcoming Maven release? Thanks, Matt > Create a tool that will generate an archetype from an existing project > -- > > Key: ARCHETYPE-31 > URL: http://jira.codehaus.org/browse/ARCHETYPE-31 > Project: Maven Archetype > Type: New Feature > Reporter: Jason van Zyl > Assignee: Jason van Zyl > Fix For: 0.7 > > > An archetype author shold be able to work/debug an existing project and when > satisfied just flip it into an archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-798) Add JBoss-client4.0.3SP1.jar
Add JBoss-client4.0.3SP1.jar Key: MAVENUPLOAD-798 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-798 Project: maven-upload-requests Type: Task Reporter: yan This is JBoss Application Server Client JBoss Application Server is a J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals. It provides the full range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62104 ] Matthew Beermann commented on MCLOVER-23: - That approach seems... unpleasant to me. You have to modify the root POM to make it work. What if each developer has different settings? They each must create their own build-tools.jar and install it into their local repo? Regardless, if this is going to be the recommended approach across a lot of projects, it might merit documentation up at http://maven.apache.org/guides/index.html... but that's a separate issue. > Allow custom license to be passed as JAR resource, URL or File > -- > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > Attachments: clover-license-fix.patch, clover.patch.txt > > > In the same way it's done in the checkstyle and PMD plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-175) ChangLogConsumer is not handling log entries from merged branches
[ http://jira.codehaus.org/browse/SCM-175?page=all ] Emmanuel Venisse closed SCM-175: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0 Applied. > ChangLogConsumer is not handling log entries from merged branches > - > > Key: SCM-175 > URL: http://jira.codehaus.org/browse/SCM-175 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-bazaar > Reporter: Torbjørn EIkli Smørgrav > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0 > Attachments: SCM-175-maven-scm-provider-bazaar.patch > > > The log entries from yourBranch after a "bzr merge yourBranch myBranch" is > not handeled, just ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62101 ] Vincent Massol commented on MCLOVER-23: --- Fixed in SVN. It would be nice if someone could validate it works. > Allow custom license to be passed as JAR resource, URL or File > -- > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > Attachments: clover-license-fix.patch, clover.patch.txt > > > In the same way it's done in the checkstyle and PMD plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62100 ] Vincent Massol commented on MCLOVER-23: --- Matthew, plugin configuration files are not placed in the repository. For example take the checkstyle xml config file. This is the same here. The idea is that you create a build-tools jar artifact which contains all your configuration files and that you can put in your local repo. See http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html. > Allow custom license to be passed as JAR resource, URL or File > -- > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > Attachments: clover-license-fix.patch, clover.patch.txt > > > In the same way it's done in the checkstyle and PMD plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-642) Error when retrieving list of projects through xmlrpc
Error when retrieving list of projects through xmlrpc - Key: CONTINUUM-642 URL: http://jira.codehaus.org/browse/CONTINUUM-642 Project: Continuum Type: Bug Versions: 1.0.3 Environment: Netbeans + mevenide's continuum integration Reporter: Milos Kleint Priority: Blocker when trying to retrieve the list of projects both from my local install and teh ci.codehaus.org server I get this exception sent to me by the server. I'm using the mevenide's own rpc client code (that I contributed to continuum) but that makes no difference IMHO. key=result failure key=stackTrace org.jpox.exceptions.ClassNotResolvedException: Class org.apache.maven.continuum.model.project.Project was not found in the CLASSPATH. Please check your specification and your CLASSPATH. at org.jpox.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:169) at org.jpox.JDOClassLoaderResolver.classForName(JDOClassLoaderResolver.java:317) at org.jpox.store.rdbms.extent.ClassTableExtent$1.getType(ClassTableExtent.java:210) at org.jpox.store.query.UnionIteratorStatement.(UnionIteratorStatement.java:186) at org.jpox.store.query.UnionIteratorStatement.(UnionIteratorStatement.java:160) at org.jpox.store.rdbms.extent.ClassTableExtent.newQueryStatement(ClassTableExtent.java:198) at org.jpox.store.query.JDOQLQuery$Compiler.executionCompile(JDOQLQuery.java:806) at org.jpox.store.query.JDOQLQuery.performExecute(JDOQLQuery.java:447) at org.jpox.store.query.Query.executeWithMap(Query.java:1113) at org.jpox.store.query.Query.executeWithArray(Query.java:1086) at org.jpox.store.query.Query.execute(Query.java:1009) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1146) at org.apache.maven.continuum.store.JdoContinuumStore.getAllProjectsWithAllDetails(JdoContinuumStore.java:1069) at org.apache.maven.continuum.DefaultContinuum.getAllProjectsWithAllDetails(DefaultContinuum.java:2149) at org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.getProjects(DefaultContinuumXmlRpc.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlrpc.Invoker.execute(Unknown Source) at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(Unknown Source) at org.apache.xmlrpc.XmlRpcWorker.execute(Unknown Source) at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source) at org.apache.xmlrpc.XmlRpcServer.execute(Unknown Source) at org.apache.xmlrpc.WebServer$Connection.run(Unknown Source) at org.apache.xmlrpc.WebServer$Runner.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) key=message Class org.apache.maven.continuum.model.project.Project was not found in the CLASSPATH. Please check your specification and your CLASSPATH. key=method ContinuumXmlRpc.getProjects() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-545) allow xmlrpc access to build results log
[ http://jira.codehaus.org/browse/CONTINUUM-545?page=comments#action_62099 ] Milos Kleint commented on CONTINUUM-545: this seems to be fixed in the current RC, one can access the build results under eg. http://localhost:8080/continuum/servlet/browse?file=2/3.log.txt > allow xmlrpc access to build results log > > > Key: CONTINUUM-545 > URL: http://jira.codehaus.org/browse/CONTINUUM-545 > Project: Continuum > Type: New Feature > Components: XMLRPC Interface > Reporter: Milos Kleint > Priority: Critical > > > currently the xmlrpc access cannot read build results, it's not included for > performance reasons. But without means of accessing it, the netbeans > integration is just half as useful. Providing an URL on the server for the > build should be enough. > irc log: > another Q: will it be possible to get the build results/output from rpc? > currently I didn't figure how.. > evenissemethod is missing in rpc server > trygvis yeah, that was deliberate > evenisseyou can add it > DefaultContinum.getBuildResult(id).getOutput() > trygvis we should make a special servlet for returning the build output > evenissewhy? due to output length? > trygvis yep > trygvis useful for the web UI anyway > trygvis I'm afraid that giving the xml-rpc stuff 20MB of logs will give > a OutOfMemoryException > evenisse20MB for an build output, pff > trygvis hehe, the geronimo build is at least that! > evenisseok, so mkleint, don't use rpc for output ;-) > mkleint can have at least the ending portion of the output log? > mkleint evenisse: kind of sucks, the IDE integration not usefule much > then.. I assumed it will be added someday.. > mkleint or produce an URL that can be opened on request.. > trygvis you can do a simple HTTP GET to get it > trygvis right :) > mkleint how to construct the URL? > trygvis it's not implemented, but probably root>/build-output/ > mkleint btw I'm also not getting the list of builds in rpc at all.. a > bug or not implemented either? > evenissewith 1.0.* > http://server/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=BUILD_RESULT_I&id=PROJECT_ID > evenisseand get on it only what you need > <--|jsisson has left #continuum (jsisson) > trygvis won't that give you an entire html page= > trygvis ? > evenisseyes :) > evenissebut output is after "Output" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-3) Links in File Activity Report can be wrong when using subversion, after a copy command has been issued
[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=comments#action_62097 ] Julian Wood commented on MCHANGELOG-3: -- Found it. http://svn.apache.org/viewcvs.cgi/maven/sandbox/plugins/ J > Links in File Activity Report can be wrong when using subversion, after a > copy command has been issued > -- > > Key: MCHANGELOG-3 > URL: http://jira.codehaus.org/browse/MCHANGELOG-3 > Project: Maven 2.x Changelog Plugin > Type: Bug > Environment: OSX 10.4.3, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > Fix For: 2.0 > Attachments: MOJO-216-changelog-maven-plugin-1a.patch, > MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt > > > When you do a subversion copy command, the list of files produced by svn log > often have additional information that is part of the filename: > R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) > In SvnChangeLogParser.java, the file name is parsed as > /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of > course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most > significantly manifested when a link is generated, such as in the File > Activity Report. > http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128) > I can see two approaches to the problem. The simplest is to add a regular > expression which deletes the extraneous data, but then you lose that > potentially valuable information. Maybe ChangeLogFile should keep track of a > file (path) and a name, rather than just a name, so that the link can be made > properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-3) Links in File Activity Report can be wrong when using subversion, after a copy command has been issued
[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=comments#action_62096 ] Julian Wood commented on MCHANGELOG-3: -- Umm, where did changelog go? It used to be at mojo: https://svn.mojo.codehaus.org/mojo/trunk/mojo/changes-maven-plugin I can see Brett deleted it the other day at revision 1710. In rev 1711 a changelog-maven-plugin folder was added to the /trunk/mojo/mojo-site/src/site/resources directory, but it is empty with the exception of .htacesss, and is likely just for docs anyway. Has it also been migrated into (as well as changed to use) maven-scm? I don't see it here either: http://svn.apache.org/viewcvs.cgi/maven/plugins/trunk/ or here http://svn.apache.org/viewcvs.cgi/maven/scm/trunk Whither has it gone? I guess I'm missing something. Thanks, J > Links in File Activity Report can be wrong when using subversion, after a > copy command has been issued > -- > > Key: MCHANGELOG-3 > URL: http://jira.codehaus.org/browse/MCHANGELOG-3 > Project: Maven 2.x Changelog Plugin > Type: Bug > Environment: OSX 10.4.3, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Edwin Punzalan > Priority: Minor > Fix For: 2.0 > Attachments: MOJO-216-changelog-maven-plugin-1a.patch, > MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt > > > When you do a subversion copy command, the list of files produced by svn log > often have additional information that is part of the filename: > R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) > In SvnChangeLogParser.java, the file name is parsed as > /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of > course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most > significantly manifested when a link is generated, such as in the File > Activity Report. > http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128) > I can see two approaches to the problem. The simplest is to add a regular > expression which deletes the extraneous data, but then you lose that > potentially valuable information. Maybe ChangeLogFile should keep track of a > file (path) and a name, rather than just a name, so that the link can be made > properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-365) Please Add JTOpen 5.0 to ibiblio
Please Add JTOpen 5.0 to ibiblio Key: MEV-365 URL: http://jira.codehaus.org/browse/MEV-365 Project: Maven Evangelism Type: Improvement Reporter: K.C. Baltz I'm not a developer of the JTOpen libraries, but I do use them. Versions 4.7-4.9 are in ibiblio, so it seems logical to simply add 5.0.0. Sorry if I'm asking in the wrong place or providing insufficient files. Let me know if more legwork is required. Proposed pom.xml 4.0.0 net.sf.jt400 jt400-full 5.0.0 jar JT400 http://jt400.sourceforge.net/ http://cvs.sourceforge.net/viewcvs.py/jt400/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-240) Absolute links bypass mod_proxy
[ http://jira.codehaus.org/browse/CONTINUUM-240?page=comments#action_62092 ] Anders Johan Jamtli commented on CONTINUUM-240: --- Relative URLs are usually a good idea. Using HTTPS and mod_proxy seem to be a problem. Since there is no proxy-https-listener, at least not that I can find, the connection between mod_proxy and continuum proxy listener has to be HTTP: ProxyPass /continuum/ http://localhost:8090/continuum/ ProxyPassReverse /continuum/ http://localhost:8090/continuum/ And with the following proxy-http-listener configuration: 8090 www.test.com 443 Continuum will produce the following URLs: http://www.test.com:443/continuum/css/tigris.css which again result in a "400 Bad Request" because the browser is speaking plain HTTP to a HTTPS port. > Absolute links bypass mod_proxy > > > Key: CONTINUUM-240 > URL: http://jira.codehaus.org/browse/CONTINUUM-240 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0-alpha-3 > Reporter: Björn Sköld > Assignee: Trygve Laugstol > Priority: Minor > Fix For: 1.0-alpha-4 > > > Continuum does not work with the mod_proxy config shown in site docs: > ProxyPass /continuum http://localhost:8080/continuum/ > ProxyPassReverse /continuum http://localhost:8080/continuum/ > All links in the continuum webapp are absolute, and ProxyPassReverse only > does rewrite of headers, not page content. > This means that clicking on one of continuums links bypasses the proxy and > goes directly to localhost:8080/continuum/. > There is a 3rd-party module (mod_proxy_html) that does rewrite of page > content, but it seems like a waste of CPU cycles. > Making continuum generate relative links would probably be more efficient. > http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypassreverse -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-22) Always generates groupId directories
[ http://jira.codehaus.org/browse/ARCHETYPE-22?page=comments#action_62090 ]
Adolfo Garcia commented on ARCHETYPE-22:
I came across this issue while writing an archetype for web applications that
use Hibernate. I wanted to place the example entity Entity.java in the package
${groupId}.entity, i.e. in the directory
/src/main/java/${groupId}/entity/Entity.java, but was unable
to do it. What I got was the package entity.${groupId}, which may no be
desirable.
> Always generates groupId directories
>
>
> Key: ARCHETYPE-22
> URL: http://jira.codehaus.org/browse/ARCHETYPE-22
> Project: Maven Archetype
> Type: Wish
> Reporter: Eric Redmond
> Assignee: Jason van Zyl
>
>
> I'd like to see the source directories explicity define groupId based
> directory structure. For example:
> /src/main/java/App.java
> would generate /src/main/java/App.java,
> But something similar to /src/main/java/${groupId}/App.java
> would generate the directory structure as it is generated today.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (MNGECLIPSE-94) Not downloading newer version of xxx-SNAPSHOT-sources.jar
Not downloading newer version of xxx-SNAPSHOT-sources.jar - Key: MNGECLIPSE-94 URL: http://jira.codehaus.org/browse/MNGECLIPSE-94 Project: Maven 2.x Extension for Eclipse Type: Bug Versions: 0.0.5 Reporter: Federico Assigned to: Eugene Kuleshov Priority: Minor We are able to have java sources automatically downloaded and associated with related class files in Eclipse. We only have a problem when working with SNAPSHOT projects and if another developer deploy on the server a new release of the jar and its java.sources.jar file. We have selected (enabled) the "Update Snapshots" and "Download Artifact Sources" options On the Maven Repository we see the newer xxx-0.5-SNAPSHOT.jar, its POM and its sources.jar files as following: xxx-0.5-20060327.145000-13-sources.jar 27-Mar-2006 16:49 4k xxx-0.5-20060327.145000-13-sources.jar.md527-Mar-2006 16:49 1k xxx-0.5-20060327.145000-13-sources.jar.sha127-Mar-2006 16:49 1k xxx-0.5-20060327.145000-13.jar 27-Mar-2006 16:49 21k xxx-0.5-20060327.145000-13.jar.md5 27-Mar-2006 16:49 1k xxx-0.5-20060327.145000-13.jar.sha1 27-Mar-2006 16:49 1k xxx-0.5-20060327.145000-13.pom 27-Mar-2006 16:49 2k xxx-0.5-20060327.145000-13.pom.md527-Mar-2006 16:49 1k xxx-0.5-20060327.145000-13.pom.sha1 27-Mar-2006 16:49 1k if I edit and save the POM with a dependency to xxx-0.5-SNAPSHOT I receive the following files in my local repository: xxx-0.5-SNAPSHOT-sources.jar xxx-0.5-SNAPSHOT.jar xxx-0.5-SNAPSHOT.pom but if I already have those files (from an older SNAPSHOT release) m2eclipse only updates the following files: xxx-0.5-SNAPSHOT.jar xxx-0.5-SNAPSHOT.pom if I then delete the xxx-0.5-SNAPSHOT-sources.jar file and edit and save again the pom.xml the new sources are downloaded. is there any plugin in maven itself for downloading java sources from the repo and install them locally? we could use it as a workaround compliments for the nice work you are doing, thanks in advance, Federico -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-793) xreporter expression library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-793?page=comments#action_62089 ] Jorg Heymans commented on MAVENUPLOAD-793: -- org.outerj.xreporter is the root package name of the code. > xreporter expression library > > > Key: MAVENUPLOAD-793 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-793 > Project: maven-upload-requests > Type: Task > Reporter: Jorg Heymans > > > please add to ibiblio/maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-3) site adds relative paths to css, etc, but doesn't work for error documents
[ http://jira.codehaus.org/browse/MSITE-3?page=comments#action_62088 ] Jesse McConnell commented on MSITE-3: - brett, I don't see any .htaccess file in src/site/resources... do you think we ought to just switch things over to absolution urls in here? > site adds relative paths to css, etc, but doesn't work for error documents > -- > > Key: MSITE-3 > URL: http://jira.codehaus.org/browse/MSITE-3 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Brett Porter > Fix For: 2.0 > > > we should possibly use the absolute urls for these anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-795) daisy html cleaner library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-795?page=comments#action_62087 ] Jorg Heymans commented on MAVENUPLOAD-795: -- org.outerj.daisy is the root package name of the code. > daisy html cleaner library > -- > > Key: MAVENUPLOAD-795 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-795 > Project: maven-upload-requests > Type: Task > Reporter: Jorg Heymans > > > please add to ibiblio/maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62086 ] Matthew Beermann commented on MCLOVER-23: - At the risk of being dense, with this patch, where exactly in my team's (internal) remote repository would I want to place the license, and with what value for to make it work? > Allow custom license to be passed as JAR resource, URL or File > -- > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > Attachments: clover-license-fix.patch, clover.patch.txt > > > In the same way it's done in the checkstyle and PMD plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPJAR-52) Cannot override Implementation-Version attribute in Manifest via a properties file
[ http://jira.codehaus.org/browse/MPJAR-52?page=comments#action_62085 ] Anna Nicotera commented on MPJAR-52: For now my workaround is updating theplugin.jelly file to and set it there (which means all of my jars will have that) but for now, it's ok, until we have the fix to be able to override properties. Thanks for looking into it. > Cannot override Implementation-Version attribute in Manifest via a properties > file > -- > > Key: MPJAR-52 > URL: http://jira.codehaus.org/browse/MPJAR-52 > Project: maven-jar-plugin > Type: Bug > Versions: 1.7 > Environment: Windows XP SP2; SunOS 5.9;Linux RedHat 2.4.21-32.0.ELsmp; Maven > 1.0.2 (Problem occurs on all these platforms) > Reporter: Anna Nicotera > Priority: Critical > Fix For: 1.8 > Attachments: project.properties > > > When using maven-jar-plugin-1.7.1.jar, when I try to override the Manifest's > Implementation-Version via a project.properties file, the resulting Manifest > is unchanged (always seems to take what is specified in the plugin.jelly). > This was not a problem when I was using maven-jar-plugin-1.6.1.jar. When I > was using maven-jar-plugin-1.6.1.jar, the Implementation-Version attribute > was being set to whatever I set in my project.properties file. > This is the EXPECTED manifest file contents (produced when using > maven-jar-plugin-1.6.1.jar. ): > Manifest-Version: 1.0 > Ant-Version: Apache Ant 1.5.3 > Created-By: Apache Maven > Built-By: axp > Package: > Build-Jdk: 1.4.2_08 > Class-Path: AdvCommon.jar Advisor.jar AdvisorSvr.jar ClusteringFramew > ork.jar record-1.0.jar sourcegen_workaround.jar extensions-3.0.jar i1 > 8n-3.0.jar mb-resources-3.0.jar mb-messages-3.0.jar df-messages-3.0.j > ar df-resources-3.0.jar scheduler-spi-3.0.jar antlr-2.7.5H3.jar commo > ns-vfs-1.0-RC4.jar commons-collections-3.1.jar commons-logging-api-1. > 0.2.jar ecs.jar ant-antlr-1.6.5.jar bsh-2.0b1.jar bsf-2.3.jar colt.ja > r cglib-2.1.2.jar javassist-3.0.jar dom4j-1.6.1.jar castor-0.9.3.9.ja > r foxtrot-2.0.jar getopt-1.0.9.jar java_readline.jar trove.jar hibern > ate3.jar htmlparser-1.41.jar jide-1.8.3.05.jar forms-1.0b2.jar jdom-1 > .0beta9.jar jstyle.jar jloox-3.0.jar jlayout-1.3.jar nb-editor.jar as > m.jar asm-attrs.jar oro-2.0.8.jar concurrent-1.3.4.jar jcchartK-5.0.j > ar jdnc-0.5-all.jar jacl.jar tcljava.jar j2printerworks-3.2.jar xml-a > pis-1.0.jar xercesImpl-2.7.0.jar xerces-1.3.1.jar ZKM.jar velocity-1. > 4.jar velocity-dep-1.4.jar > Extension-Name: mb > Specification-Title: ModelBuilder executable > Specification-Vendor: Fair Isaac Corporation > Implementation-Title: > Implementation-Vendor: Fair Isaac Corporation > Implementation-Version: 3.0.0.dev > This is the actual Manifest file contents (produced when using > maven-jar-plugin-1.7.1.jar): > Manifest-Version: 1.0 > Ant-Version: Apache Ant 1.5.3 > Created-By: Apache Maven > Built-By: axp > Package: > Build-Jdk: 1.4.2_08 > Class-Path: AdvCommon.jar Advisor.jar AdvisorSvr.jar ClusteringFramew > ork.jar record-1.0.jar sourcegen_workaround.jar extensions-3.0.jar i1 > 8n-3.0.jar mb-resources-3.0.jar mb-messages-3.0.jar df-messages-3.0.j > ar df-resources-3.0.jar scheduler-spi-3.0.jar antlr-2.7.5H3.jar commo > ns-vfs-1.0-RC4.jar commons-collections-3.1.jar commons-logging-api-1. > 0.2.jar ecs.jar ant-antlr-1.6.5.jar bsh-2.0b1.jar bsf-2.3.jar colt.ja > r cglib-2.1.2.jar javassist-3.0.jar dom4j-1.6.1.jar castor-0.9.3.9.ja > r foxtrot-2.0.jar getopt-1.0.9.jar java_readline.jar trove.jar hibern > ate3.jar htmlparser-1.41.jar jide-1.8.3.05.jar forms-1.0b2.jar jdom-1 > .0beta9.jar jstyle.jar jloox-3.0.jar jlayout-1.3.jar nb-editor.jar as > m.jar asm-attrs.jar oro-2.0.8.jar concurrent-1.3.4.jar jcchartK-5.0.j > ar jdnc-0.5-all.jar jacl.jar tcljava.jar j2printerworks-3.2.jar xml-a > pis-1.0.jar xercesImpl-2.7.0.jar xerces-1.3.1.jar ZKM.jar velocity-1. > 4.jar velocity-dep-1.4.jar > Extension-Name: mb > Specification-Title: ModelBuilder executable > Specification-Vendor: Fair Isaac Corporation > Implementation-Title: > Implementation-Vendor: Fair Isaac Corporation > Implementation-Version: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCLOVER-23) Allow custom license to be passed as JAR resource, URL or File
[ http://jira.codehaus.org/browse/MCLOVER-23?page=all ] Vincent Massol updated MCLOVER-23: -- Description: In the same way it's done in the checkstyle and PMD plugins. (was: It would be nice to share a custom license between different project. A solution is to create a new artifact type and put the license in the local/remote repositories and specify it using a dependency as any other artifact. Idea suggested by Matthew Beermann. ) Fix Version: 2.1 Summary: Allow custom license to be passed as JAR resource, URL or File (was: Allow custom license to be put in the repository) > Allow custom license to be passed as JAR resource, URL or File > -- > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 2.1 > Attachments: clover-license-fix.patch, clover.patch.txt > > > In the same way it's done in the checkstyle and PMD plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be put in the repository
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62084 ] Vincent Massol commented on MCLOVER-23: --- Thanks John. It seems we've both been working on it at exactly the same time as I've also just finished implementing it :-) > Allow custom license to be put in the repository > > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Attachments: clover-license-fix.patch, clover.patch.txt > > > It would be nice to share a custom license between different project. A > solution is to create a new artifact type and put the license in the > local/remote repositories and specify it using a dependency as any other > artifact. Idea suggested by Matthew Beermann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCLOVER-23) Allow custom license to be put in the repository
[ http://jira.codehaus.org/browse/MCLOVER-23?page=all ] John Allen updated MCLOVER-23: -- Attachment: clover-license-fix.patch > Allow custom license to be put in the repository > > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Attachments: clover-license-fix.patch, clover.patch.txt > > > It would be nice to share a custom license between different project. A > solution is to create a new artifact type and put the license in the > local/remote repositories and specify it using a dependency as any other > artifact. Idea suggested by Matthew Beermann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-796) Upload of new version of rmock 2.0.0-rc-6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-796?page=comments#action_62081 ] Daniel Brolund commented on MAVENUPLOAD-796: I did that last time, see http://jira.codehaus.org/browse/MAVENUPLOAD-741 for details. Should I reference that in future for your convenience? Cheers Daniel > Upload of new version of rmock 2.0.0-rc-6 > - > > Key: MAVENUPLOAD-796 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-796 > Project: maven-upload-requests > Type: Task > Reporter: Daniel Brolund > > > rMock 2.0.0 is a Java mock object framework to use with jUnit. > rMock has support for a setup-modify-run-verify workflow when writing jUnit > tests. > It integrates better with IDE refactoring support and allows designing classes > and interfaces in a true test-first fashion. rMock has the flexibility and > power of jMock, while the recording of mock calls is influenced by EasyMock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2183) Create some plugin library for passing configuration resources
Create some plugin library for passing configuration resources -- Key: MNG-2183 URL: http://jira.codehaus.org/browse/MNG-2183 Project: Maven 2 Type: Improvement Components: Plugin API Versions: 2.0.3 Reporter: Vincent Massol The checkstyle and PMD plugins allow passing configuration resources using different mechanisms (URL, file, resources in a JAR). They both duplicate lot of code (and especially the Locator class). I think all plugins requiring configuration resources to be passed would benefit from a library and usage consistency would be improved. I'm going to implement this for the Clover plugin too and for now I'll duplicate the Locator class too... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-85) cvs protocol not supported ?
[ http://jira.codehaus.org/browse/MRELEASE-85?page=all ] Emmanuel Venisse closed MRELEASE-85: Assign To: Emmanuel Venisse Resolution: Won't Fix cvs is supported and it was the first with svn. Please ask the user list if you have some questions > cvs protocol not supported ? > > > Key: MRELEASE-85 > URL: http://jira.codehaus.org/browse/MRELEASE-85 > Project: Maven 2.x Release Plugin > Type: New Feature > Versions: 2.0-beta-3 > Reporter: Christophe Lallement > Assignee: Emmanuel Venisse > > > I'm surprised that maven release plugin does'nt support CVS protocol within > scm url ? > When looking at source => helpers/ScmHelper.java CVS seems to be unsupported > (method getScmRepository) > So CVS is intensive used in my company and it should be fine to support this > scm (so, cvs is supported into maven-scm-plugin) > Thx > Christophe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-797) Add sources to commons-validator 1.3.0
Add sources to commons-validator 1.3.0 -- Key: MAVENUPLOAD-797 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-797 Project: maven-upload-requests Type: Improvement Reporter: Tomislav Stojcevich Attachments: commons-validator-1.3.0-bundle.jar Add sources only from bundle to commons-validator 1.3.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be put in the repository
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62079 ] Vincent Massol commented on MCLOVER-23: --- Hi Matthew, Your patch is not quite correct. You're not allowed to put any file in your local repository. This is an area reserved by Maven2 (it was open in Maven1). You have to go through Maven2 to put a file there. Thus the only solution to put a file there is to define a new artifact type. The other reason is that if you're working within a team you'll want to upload this file to your remote repository. Hi John, Yes you're right: using the same mechanism is the best solution. This allows putting the license file in a shared JAR. Better and more consistent than what I was proposing. > Allow custom license to be put in the repository > > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Attachments: clover.patch.txt > > > It would be nice to share a custom license between different project. A > solution is to create a new artifact type and put the license in the > local/remote repositories and specify it using a dependency as any other > artifact. Idea suggested by Matthew Beermann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2182) site:deploy will fail if site url is file:// and directory is non-empty
site:deploy will fail if site url is file:// and directory is non-empty --- Key: MNG-2182 URL: http://jira.codehaus.org/browse/MNG-2182 Project: Maven 2 Type: Bug Components: Sites & Reporting Versions: 2.0.2 Environment: win2k Reporter: Matt Munz The first time I run site:deploy, all is fine. The second time, I get the following error. Embedded error: Could not make directory '\\myFileServer\path\to\project\website\.'. If I delete this directory, site:deploy works as expected. My POM contains this fragment. website my project website file:myFileServer/path/to/project/website/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPCASTOR-11) automated builds hang when castor warnings are on
[ http://jira.codehaus.org/browse/MPCASTOR-11?page=comments#action_62077 ] Lukas Theussl commented on MPCASTOR-11: --- Please note that the castor plugin is currently not maintained by the Maven team anymore. It has been deprecated after Maven-1.1-beta2 and will not be distributed with Maven-1.1 anymore. See http://maven.apache.org/maven-1.x/reference/backwards-compatibility.html. > automated builds hang when castor warnings are on > - > > Key: MPCASTOR-11 > URL: http://jira.codehaus.org/browse/MPCASTOR-11 > Project: maven-castor-plugin > Type: Bug > Environment: running from anthill pro 2.5 on solaris > Reporter: jake pezaro > Priority: Minor > > > enabling castor warnings causes castor to prompt the user when overwriting > generated source files. in situations where the source directory cannot be > cleaned (eg when running the clover report plugin) this causes the automated > build to hang. > this can be worked aroud by turning the warnings off, however this causes > castor overwrite files with name clashes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-23) Allow custom license to be put in the repository
[ http://jira.codehaus.org/browse/MCLOVER-23?page=comments#action_62076 ] Matthew Beermann commented on MCLOVER-23: - The thing is, the manufacturer of Clover specifies a particular algorithm that will be used to locate the Clover license, and I think we should strive for parity with that. Check the bottom of the page at: http://www.cenqua.com/clover/doc/ > Allow custom license to be put in the repository > > > Key: MCLOVER-23 > URL: http://jira.codehaus.org/browse/MCLOVER-23 > Project: Maven 2.x Clover Plugin > Type: Task > Versions: 2.0 > Reporter: Vincent Massol > Attachments: clover.patch.txt > > > It would be nice to share a custom license between different project. A > solution is to create a new artifact type and put the license in the > local/remote repositories and specify it using a dependency as any other > artifact. Idea suggested by Matthew Beermann. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGONHTTP-9) unable to use wagon-http-lightweight with maven deploy and release plugins
[ http://jira.codehaus.org/browse/WAGONHTTP-9?page=all ] Brett Porter closed WAGONHTTP-9: Assign To: Brett Porter Resolution: Fixed Fix Version: 1.0-alpha-7 applied, thanks > unable to use wagon-http-lightweight with maven deploy and release plugins > -- > > Key: WAGONHTTP-9 > URL: http://jira.codehaus.org/browse/WAGONHTTP-9 > Project: wagon-http > Type: Bug > Versions: 1.0-alpha-6 > Environment: maven 2.0.2 on windows xp. > Reporter: ysoonleo > Assignee: Brett Porter > Fix For: 1.0-alpha-7 > Attachments: wagon-http-lightweight.patch > > > The wagon-http-lightweight fails with response 201 and 204 when using maven > deploy and release:perform plugins. > The error messages are: > [INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection > returned the response code: 201 > [INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection > returned the response code: 204 > The wagon-http-lightweight fails because it only handles response code 200 > and flags the rest as errors. > The attached patch file should address this problem as it uses the same code > handling mechanism from wagon-http. This patch can also be used to address > the WAGONHTTP-7 issue for wagon-http. > With this patch, the wagon-http and wagon-http-lightweight.will work with > webdav for the deploy and release plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-641) stopping continuum when builds are in progress /queued causes duplicates on restart
stopping continuum when builds are in progress /queued causes duplicates on restart --- Key: CONTINUUM-641 URL: http://jira.codehaus.org/browse/CONTINUUM-641 Project: Continuum Type: Task Components: Core system Versions: 1.0.3 Reporter: Brett Porter Priority: Blocker Fix For: 1.0.3 I was able to reliably reproduce this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=comments#action_62069 ] Andrew Perepelytsya commented on MIDEA-39: -- I don't think that's a 100% solution. When I have 30 something modules in the project I can generate idea files as you said, once. Then, when 1 module is added, I really want to have an option whether to generate it with the libs or with project dependencies. I guess poms contain all the information requried to have this kind of functinality. To make things worse, some latest IDEA builds have HUGE problems if you have both library jars and project dependencies (sources), resulting in debug breakpoints being skipped altogether (read, impossible to debug anything). > In a multi-module project, idea plugin should generate module dependencies > instead of creating libs with references to the repository > - > > Key: MIDEA-39 > URL: http://jira.codehaus.org/browse/MIDEA-39 > Project: Maven 2.x Idea Plugin > Type: Improvement > Versions: 2.0 > Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 > Reporter: Vikash Ramanlal > Assignee: Brett Porter > Priority: Minor > > > When I generate my idea files using "mvn idea:idea", all works fine. > However if I have module a and module b (both jar packaging) and b depends on > a, then I expected the idea plugin to generate the project files such that > for module b, a is a dependent module. However what I get is a library entry > for a that points to a jar in the local repository. > Maven 1.0.2 idea plugin did not work this way. I created the module > dependencies in correctly in the idea project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPCASTOR-11) automated builds hang when castor warnings are on
automated builds hang when castor warnings are on - Key: MPCASTOR-11 URL: http://jira.codehaus.org/browse/MPCASTOR-11 Project: maven-castor-plugin Type: Bug Environment: running from anthill pro 2.5 on solaris Reporter: jake pezaro Priority: Minor enabling castor warnings causes castor to prompt the user when overwriting generated source files. in situations where the source directory cannot be cleaned (eg when running the clover report plugin) this causes the automated build to hang. this can be worked aroud by turning the warnings off, however this causes castor overwrite files with name clashes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPA-48) migrate all maven, mojo, mrm, continuum, etc projects to the new workflow where closed issues can be edited.
[ http://jira.codehaus.org/browse/MPA-48?page=all ] Brett Porter closed MPA-48: --- Assign To: Brett Porter (was: Jason van Zyl) Resolution: Fixed > migrate all maven, mojo, mrm, continuum, etc projects to the new workflow > where closed issues can be edited. > > > Key: MPA-48 > URL: http://jira.codehaus.org/browse/MPA-48 > Project: Maven Project Administration > Type: Task > Components: Issue Management > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2006-q1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPA-57) migrate all Maven projects to the Basic Issue Creation Scheme in JIRA
migrate all Maven projects to the Basic Issue Creation Scheme in JIRA - Key: MPA-57 URL: http://jira.codehaus.org/browse/MPA-57 Project: Maven Project Administration Type: Task Components: Issue Management Reporter: Brett Porter Assigned to: Jason van Zyl Fix For: 2006-q1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPA-20) create release issues for each plugin to track votes and preparedness
[ http://jira.codehaus.org/browse/MPA-20?page=all ] Brett Porter closed MPA-20: --- Assign To: Brett Porter Resolution: Won't Fix Fix Version: (was: 2006-q1) > create release issues for each plugin to track votes and preparedness > - > > Key: MPA-20 > URL: http://jira.codehaus.org/browse/MPA-20 > Project: Maven Project Administration > Type: Task > Components: Issue Management > Reporter: John Casey > Assignee: Brett Porter > Priority: Blocker > > > should be specific to one release of one plugin, and should incorporate links > to all outstanding issues for that release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPA-56) Process Fabrice Bellingard
Process Fabrice Bellingard -- Key: MPA-56 URL: http://jira.codehaus.org/browse/MPA-56 Project: Maven Project Administration Type: Task Components: New Committers Reporter: Brett Porter Assigned to: Jason van Zyl Fix For: 2006-q1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPA-55) add committer Chris Stevenson
[ http://jira.codehaus.org/browse/MPA-55?page=all ] Brett Porter closed MPA-55: --- Assign To: Brett Porter (was: Jason van Zyl) Resolution: Fixed > add committer Chris Stevenson > - > > Key: MPA-55 > URL: http://jira.codehaus.org/browse/MPA-55 > Project: Maven Project Administration > Type: Task > Components: New Committers > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2006-q1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPA-55) add committer Chris Stevenson
add committer Chris Stevenson - Key: MPA-55 URL: http://jira.codehaus.org/browse/MPA-55 Project: Maven Project Administration Type: Task Components: New Committers Reporter: Brett Porter Assigned to: Jason van Zyl Fix For: 2006-q1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPA-54) create account for Brian Fox
create account for Brian Fox Key: MPA-54 URL: http://jira.codehaus.org/browse/MPA-54 Project: Maven Project Administration Type: Task Components: New Committers Reporter: Brett Porter Assigned to: Brett Porter Fix For: 2006-q1 adding for the records -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-30) checkstyle ignores cacheFile
[ http://jira.codehaus.org/browse/MCHECKSTYLE-30?page=comments#action_62067 ] Brian Fox commented on MCHECKSTYLE-30: -- Oops, I misread your first comment and didn't pick up the property reference. That will work, thanks. > checkstyle ignores cacheFile > > > Key: MCHECKSTYLE-30 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-30 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Reporter: Brian Fox > Assignee: Edwin Punzalan > > > I'm using a version of checkstyle from svn so I can get custom configuration. > The cacheFile seems to be ignored. I tried setting it even though it has a > default value, but I nver see the checkstyle-cachefile get created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-30) checkstyle ignores cacheFile
[ http://jira.codehaus.org/browse/MCHECKSTYLE-30?page=comments#action_62062 ] Edwin Punzalan commented on MCHECKSTYLE-30: --- Why can't you not use $(outputDirectory} ? cacheFile is settable in your pom.xml. > checkstyle ignores cacheFile > > > Key: MCHECKSTYLE-30 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-30 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Reporter: Brian Fox > Assignee: Edwin Punzalan > > > I'm using a version of checkstyle from svn so I can get custom configuration. > The cacheFile seems to be ignored. I tried setting it even though it has a > default value, but I nver see the checkstyle-cachefile get created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-30) checkstyle ignores cacheFile
[ http://jira.codehaus.org/browse/MCHECKSTYLE-30?page=comments#action_62059
]
Brian Fox commented on MCHECKSTYLE-30:
--
This is my current workaround, but it really should be settable in the pom. As
it is now, I need to hard code the relative location of where I want it because
I can't use maven properties like ${outputDirectory}. This also means that I
would need to maintain a separate configuration file for any projects that
don't have the same layout. This would also be solved by having the config in
the pom.
In short, it works for now, but it just doesn't feel right to need to have
information about my build structure outside the pom.
> checkstyle ignores cacheFile
>
>
> Key: MCHECKSTYLE-30
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-30
> Project: Maven 2.x Checkstyle Plugin
> Type: Bug
> Reporter: Brian Fox
> Assignee: Edwin Punzalan
>
>
> I'm using a version of checkstyle from svn so I can get custom configuration.
> The cacheFile seems to be ignored. I tried setting it even though it has a
> default value, but I nver see the checkstyle-cachefile get created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=all ] Brett Porter closed MIDEA-39: - Assign To: Brett Porter Resolution: Won't Fix if you generate everything togehter, they get linked. > In a multi-module project, idea plugin should generate module dependencies > instead of creating libs with references to the repository > - > > Key: MIDEA-39 > URL: http://jira.codehaus.org/browse/MIDEA-39 > Project: Maven 2.x Idea Plugin > Type: Improvement > Versions: 2.0 > Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 > Reporter: Vikash Ramanlal > Assignee: Brett Porter > Priority: Minor > > > When I generate my idea files using "mvn idea:idea", all works fine. > However if I have module a and module b (both jar packaging) and b depends on > a, then I expected the idea plugin to generate the project files such that > for module b, a is a dependent module. However what I get is a library entry > for a that points to a jar in the local repository. > Maven 1.0.2 idea plugin did not work this way. I created the module > dependencies in correctly in the idea project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MIDEA-36) Multi-module vs. Single-module projects
[ http://jira.codehaus.org/browse/MIDEA-36?page=all ] Brett Porter closed MIDEA-36: - Assign To: Brett Porter Resolution: Won't Fix > Multi-module vs. Single-module projects > --- > > Key: MIDEA-36 > URL: http://jira.codehaus.org/browse/MIDEA-36 > Project: Maven 2.x Idea Plugin > Type: Bug > Reporter: Aleksandr Tarutin > Assignee: Brett Porter > > > In IDEA's single module project the module files (.iml) are created at the > same level that the project file (.ipr). > For multi-mudile projects the directory containing the project file does not > contain module files but rather contains module subdirectories each > containing the module file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MIDEA-34) Add resources to source folders instead of module libraries
[ http://jira.codehaus.org/browse/MIDEA-34?page=all ] Brett Porter updated MIDEA-34: -- Fix Version: 2.0 > Add resources to source folders instead of module libraries > --- > > Key: MIDEA-34 > URL: http://jira.codehaus.org/browse/MIDEA-34 > Project: Maven 2.x Idea Plugin > Type: Bug > Versions: 2.0 > Reporter: Manfred Geiler > Priority: Critical > Fix For: 2.0 > Attachments: idea-1.patch > > > Having the resources as module libraries does not make much sense. > Instead the resources dir(s) should be added as normal idea source folders, > so that editing of properties files, xml files, etc. is possible. > see applied patch > Regards, > Manfred -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHECKSTYLE-30) checkstyle ignores cacheFile
[ http://jira.codehaus.org/browse/MCHECKSTYLE-30?page=all ] Edwin Punzalan closed MCHECKSTYLE-30: - Resolution: Won't Fix Fix Version: (was: 2.0.1) > checkstyle ignores cacheFile > > > Key: MCHECKSTYLE-30 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-30 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Reporter: Brian Fox > Assignee: Edwin Punzalan > > > I'm using a version of checkstyle from svn so I can get custom configuration. > The cacheFile seems to be ignored. I tried setting it even though it has a > default value, but I nver see the checkstyle-cachefile get created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2181) Problem with reactor when using attached goal
[ http://jira.codehaus.org/browse/MNG-2181?page=all ]
Edwin Punzalan updated MNG-2181:
Attachment: log.txt
> Problem with reactor when using attached goal
> -
>
> Key: MNG-2181
> URL: http://jira.codehaus.org/browse/MNG-2181
> Project: Maven 2
> Type: Bug
> Reporter: Vincent Massol
> Attachments: log.txt
>
>
> Here's my project dir structure:
> {noformat}
> trunk/
> |_ core/
> |_ api/
> |_ (several projects here)
> |_ uberjar/ (assembly project)
> |_ samples
> |_ testdata
> |_ empty-jar
> |_ (...)
> {noformat}
> If I build the trunk/core/ubjerjar project alone it works fine. Note: I have
> attached the "attached" goal to the verify phase so the assembly can be
> created when calling "mvn install".
> If I build the project from the trunk by typing "mvn install", the uberjar/
> project fails saying that the empty-jar artifact cannot be found in the local
> repository. That's normal it cannot be found because there are no
> dependencies on it in the core/ branch and it hasn't been built yet when the
> uberjar project executes. Of course there are no dependencies to it in the
> uberjar project.
> It seems there's something fishy happening in the assembly plugin
> implementation... :-)
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Moved: (MNG-2181) Problem with reactor when using attached goal
[ http://jira.codehaus.org/browse/MNG-2181?page=all ]
Edwin Punzalan moved MASSEMBLY-12 to MNG-2181:
--
Fix Version: (was: 2.1)
Key: MNG-2181 (was: MASSEMBLY-12)
Project: Maven 2 (was: Maven 2.x Assembly Plugin)
> Problem with reactor when using attached goal
> -
>
> Key: MNG-2181
> URL: http://jira.codehaus.org/browse/MNG-2181
> Project: Maven 2
> Type: Bug
> Reporter: Vincent Massol
>
>
> Here's my project dir structure:
> {noformat}
> trunk/
> |_ core/
> |_ api/
> |_ (several projects here)
> |_ uberjar/ (assembly project)
> |_ samples
> |_ testdata
> |_ empty-jar
> |_ (...)
> {noformat}
> If I build the trunk/core/ubjerjar project alone it works fine. Note: I have
> attached the "attached" goal to the verify phase so the assembly can be
> created when calling "mvn install".
> If I build the project from the trunk by typing "mvn install", the uberjar/
> project fails saying that the empty-jar artifact cannot be found in the local
> repository. That's normal it cannot be found because there are no
> dependencies on it in the core/ branch and it hasn't been built yet when the
> uberjar project executes. Of course there are no dependencies to it in the
> uberjar project.
> It seems there's something fishy happening in the assembly plugin
> implementation... :-)
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MPASPECTJ-16) aspectj:compile also compiles java files in CVS/Base
[ http://jira.codehaus.org/browse/MPASPECTJ-16?page=comments#action_62049 ]
stephane bouchet commented on MPASPECTJ-16:
---
Hi,
I am also using CVS with aspectj and i never had this issue. ( i looked in my
workspace and i don't have any CVS/Base folder ... )
It seems this directory is used by cvs with special checkouts commands, see :
http://www.cvsnt.org/pipermail/cvsnt/2005-January/016818.html
> aspectj:compile also compiles java files in CVS/Base
>
>
> Key: MPASPECTJ-16
> URL: http://jira.codehaus.org/browse/MPASPECTJ-16
> Project: maven-aspectj-plugin
> Type: Bug
> Versions: 3.2
> Reporter: Brian Jacobsen
> Priority: Minor
> Fix For: 4.0
>
>
> When using the aspect:compile goal we receive a lot of errors, because the
> jelly plugin also tries to compile java sources in CVC/Base directory.
> ---
> xxx\CVS\Base\Yyy.java:82 error The constructor ZzzException(String,
> NamingException) is undefined
> throw new ZzzException("test", e);
>
> xxx\CVS\Base\zzzException.java:6 error The type zzzException is already
> defined
> public class ZzzException extends Exception {
>
> ---
> Suggested fix:
> Use ant:srcdir instead of ant:sourceroots or make it possible to specify the
> preferred behaviour with a property.
>
>
>
>
>
>
>
> Or perhaps it is possible to bypass the problem in another way?
> regards
> Brian
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1228) ant artifact doesn't read settings.xml
[ http://jira.codehaus.org/browse/MNG-1228?page=comments#action_62050 ]
Josh Moore commented on MNG-1228:
-
isn't reading settings.xml either. We have a version
number stored in settings.xml. Error message:
[mvn:pom] An error has occurred while processing the Maven artifact tasks.
[mvn:pom] Diagnosis:
[mvn:pom]
[mvn:pom] Unable to build project: /pom.xml
[mvn:pom] The POM expression: ${omero.version} could not be evaluated.
Reason: omero:common:pom:${omero.version} references itself.
BUILD FAILED
> ant artifact doesn't read settings.xml
> --
>
> Key: MNG-1228
> URL: http://jira.codehaus.org/browse/MNG-1228
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0 (RC)
> Environment: winxp
> Reporter: Brian Fox
> Fix For: 2.0.4
>
>
> We are using an ant script to call maven deploy to auto deploy jar, pom and
> md5's and sh1's for 3rd party libraries to our remote repository. The maven
> deploy ant task isn't using the settings to find our mirrors or repositories
> for download. We have a parent pom that it should find, but it's not. The
> settings.xml is in maven/conf and in HOME/.m2/ and in HOME/.ant/
> The repositories are defined in our pom file, but the login information needs
> to be in the settings.xml. When we run this, it isn't finding the login
> information from settings. We also had an issue where the remote repositories
> where defined in settings and it wasn't working until we moved it to the pom.
> The underlying problem seems to be that settings isn't taken into account in
> either case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-30) checkstyle ignores cacheFile
[ http://jira.codehaus.org/browse/MCHECKSTYLE-30?page=comments#action_62043 ] Edwin Punzalan commented on MCHECKSTYLE-30: --- cacheFile is meant for the pre-configured checkstyle checks: sun, avalon, and turbine. If you are providing your own configuration, then you should put in your xml something like: Then whatever you put in the cacheFile parameter will override the above property. > checkstyle ignores cacheFile > > > Key: MCHECKSTYLE-30 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-30 > Project: Maven 2.x Checkstyle Plugin > Type: Bug > Reporter: Brian Fox > Assignee: Edwin Punzalan > Fix For: 2.0.1 > > > I'm using a version of checkstyle from svn so I can get custom configuration. > The cacheFile seems to be ignored. I tried setting it even though it has a > default value, but I nver see the checkstyle-cachefile get created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-790) iText, a free Java-PDF library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-790?page=all ] Carlos Sanchez closed MAVENUPLOAD-790: -- Assign To: Carlos Sanchez Resolution: Fixed Uploaded and relocated old ones to new place > iText, a free Java-PDF library > -- > > Key: MAVENUPLOAD-790 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-790 > Project: maven-upload-requests > Type: Task > Reporter: Bruno Lowagie > Assignee: Carlos Sanchez > > > iText is a free Java-PDF library. > Some older versions of iText are already present on iBiblio: > http://www.ibiblio.org/maven2/itext/itext/ > I don't know who uploaded these old version, but for the most recent iText > version, > I would like to use the newer naming conventions (see POM) so that the URL > looks like this: > http://www.ibiblio.org/maven2/com/lowagie/itext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-725) Please upload displaytag 12 tld
[ http://jira.codehaus.org/browse/MAVENUPLOAD-725?page=all ] Carlos Sanchez closed MAVENUPLOAD-725: -- Assign To: Carlos Sanchez Resolution: Won't Fix > Please upload displaytag 12 tld > --- > > Key: MAVENUPLOAD-725 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-725 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > Assignee: Carlos Sanchez > > > This is the tld distributed with displaytag 1.0 as displaytag-12.tld > I propose to store it as taglibs:displaytag:12 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-778) Please update 2.3.5 version of Freemarker library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-778?page=all ] Carlos Sanchez closed MAVENUPLOAD-778: -- Assign To: Carlos Sanchez Resolution: Incomplete > Please update 2.3.5 version of Freemarker library > - > > Key: MAVENUPLOAD-778 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-778 > Project: maven-upload-requests > Type: Improvement > Reporter: Francesco Tinti > Assignee: Carlos Sanchez > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-772) could someone upload the new JConnector 3.1.12
[ http://jira.codehaus.org/browse/MAVENUPLOAD-772?page=all ] Carlos Sanchez closed MAVENUPLOAD-772: -- Assign To: Carlos Sanchez Resolution: Incomplete > could someone upload the new JConnector 3.1.12 > -- > > Key: MAVENUPLOAD-772 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-772 > Project: maven-upload-requests > Type: Improvement > Reporter: Dave Sag > Assignee: Carlos Sanchez > > > it's not in proper bundle format, but it's available. i am not sure what the > protocol here is. am i allowed to make my own bundle of this and upload it? > probably not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-776) Test utility classes for ANT 1.6.5 (binaries and sources)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-776?page=all ] Carlos Sanchez closed MAVENUPLOAD-776: -- Assign To: Carlos Sanchez Resolution: Incomplete > Test utility classes for ANT 1.6.5 (binaries and sources) > - > > Key: MAVENUPLOAD-776 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-776 > Project: maven-upload-requests > Type: Task > Reporter: Adrian Herscu > Assignee: Carlos Sanchez > Attachments: ant-testutil-1.6.5-pom.jar > > > The ANT test utility classes are used to create unit tests for ANT task > classes. > This is not distributed as part of the binary distribution of ANT and users > are required to build it from sources. > The attached archive contains the binaries and sources of the > ant-testutil.jar for ANT 1.6.5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-783) Please upload QALAb 0.8.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-783?page=all ] Carlos Sanchez closed MAVENUPLOAD-783: -- Assign To: Carlos Sanchez Resolution: Incomplete > Please upload QALAb 0.8.0 > - > > Key: MAVENUPLOAD-783 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-783 > Project: maven-upload-requests > Type: Task > Reporter: Benoit Xhenseval > Assignee: Carlos Sanchez > Attachments: qalab-0.8.0-bundle.jar > > > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-791) Upload M12 "cayenne" and "cayenne-nodeps" bundles
[ http://jira.codehaus.org/browse/MAVENUPLOAD-791?page=all ] Carlos Sanchez closed MAVENUPLOAD-791: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload M12 "cayenne" and "cayenne-nodeps" bundles > - > > Key: MAVENUPLOAD-791 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-791 > Project: maven-upload-requests > Type: Task > Reporter: Andrus Adamchik > Assignee: Carlos Sanchez > > > Cayenne is already on ibiblio. Please upload these two new bundles: > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-1.2M12-bundle.jar > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-nodeps-1.2M12-bundle.jar > Thanks! > Andrus -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-784) Please upload maven-qalab-plugin 0.8.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-784?page=all ] Carlos Sanchez closed MAVENUPLOAD-784: -- Assign To: Carlos Sanchez Resolution: Incomplete > Please upload maven-qalab-plugin 0.8.0 > -- > > Key: MAVENUPLOAD-784 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-784 > Project: maven-upload-requests > Type: Task > Reporter: Benoit Xhenseval > Assignee: Carlos Sanchez > Attachments: maven-qalab-plugin-0.8.0-bundle.jar > > > it is a Maven 1.x plugin > Thanks! > Benoit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-787) itext-1.3.6, itext 1.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-787?page=all ] Carlos Sanchez closed MAVENUPLOAD-787: -- Assign To: Carlos Sanchez Resolution: Incomplete > itext-1.3.6, itext 1.4 > -- > > Key: MAVENUPLOAD-787 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-787 > Project: maven-upload-requests > Type: Wish > Reporter: rupert thurner > Assignee: Carlos Sanchez > > > newer versions of itext: 1.3.6, and 1.4 would be great. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-793) xreporter expression library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-793?page=comments#action_62041 ] Carlos Sanchez commented on MAVENUPLOAD-793: why org.outerj.xreporter groupId? > xreporter expression library > > > Key: MAVENUPLOAD-793 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-793 > Project: maven-upload-requests > Type: Task > Reporter: Jorg Heymans > > > please add to ibiblio/maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
