[jira] Commented: (MDEPLOY-46) "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace date.buildnumber
[ http://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95880 ] Geoffrey De Smet commented on MDEPLOY-46: - Even setting -DupdateReleaseInfo=true doesn't help, try it yourself: mvn deploy -DaltDeploymentRepository=ggg-deploy::default::file:///D:/tmp/delete/repo/ -DupdateReleaseInfo=true > "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace > date.buildnumber > -- > > Key: MDEPLOY-46 > URL: http://jira.codehaus.org/browse/MDEPLOY-46 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Geoffrey De Smet > > I 've checkouted a m2 project (spring-richclient) and deployed it to my local > repo using the altDeploymentRepository parameter (from MDEPLOY-41). > But the checkout is a SNAPSHOT version and the deployer should replace it > with something like spring-richclient-core-0.3.0-20070101.160450-2.jar > like the mvn deploy without altDeploymentRepository does, > but it doesn't: > [INFO] [deploy:deploy] > altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev > [INFO] Using alternate deployment repository > ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev > [INFO] Retrieving previous build number from ggg-dev > Uploading: > scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar > 50K uploaded -- 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: (MDEPLOY-46) "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace date.buildnumber
[ http://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95881 ] Geoffrey De Smet commented on MDEPLOY-46: - -DupdateReleaseInfo=true doesn't even seem to work on a normal: mvn deploy -DupdateReleaseInfo=true with pom ggg-deploy gggDeployment Repository file:///D:/tmp/delete/deployrepo/ ggg-dev gggDevelopment Repository file:///D:/tmp/delete/devrepo/ if the version ends in -SNAPSHOT, as it creates D:\tmp\delete\devrepo\org\springframework\richclient\spring-richclient\0.3.0-SNAPSHOT\spring-richclient-0.3.0-20070515.075943-1.pom It should be: ...\deployrepo\.. instead of devrepo and not have SNAPSHOT in it's directory name. > "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace > date.buildnumber > -- > > Key: MDEPLOY-46 > URL: http://jira.codehaus.org/browse/MDEPLOY-46 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Geoffrey De Smet > > I 've checkouted a m2 project (spring-richclient) and deployed it to my local > repo using the altDeploymentRepository parameter (from MDEPLOY-41). > But the checkout is a SNAPSHOT version and the deployer should replace it > with something like spring-richclient-core-0.3.0-20070101.160450-2.jar > like the mvn deploy without altDeploymentRepository does, > but it doesn't: > [INFO] [deploy:deploy] > altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev > [INFO] Using alternate deployment repository > ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev > [INFO] Retrieving previous build number from ggg-dev > Uploading: > scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar > 50K uploaded -- 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: (MRM-341) Add the "delete proxy connector" page and action
Add the "delete proxy connector" page and action Key: MRM-341 URL: http://jira.codehaus.org/browse/MRM-341 Project: Archiva Issue Type: Task Components: web application Affects Versions: 1.0-alpha-1 Reporter: Fabrice BELLINGARD Attachments: deleteProxyConnector.patch The JSP that ask for confirmation before deletion needs to be created and the delete method of ConfigureProxyConnectorAction needs to be implemented. I attached the patch. -- 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-1543) please upload JSR-250 (javax.annotations) 1.0 final POM
please upload JSR-250 (javax.annotations) 1.0 final POM --- Key: MAVENUPLOAD-1543 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1543 Project: maven-upload-requests Issue Type: Improvement Reporter: nicolas de loof JSR 250 commons java annotations has been voted 1.0 final on 11 May, 2006 -- 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-1543) please upload JSR-250 (javax.annotations) 1.0 final POM
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95902 ] nicolas de loof commented on MAVENUPLOAD-1543: -- Sorry, I made a typo on URL : http://ndeloof.free.fr/maven2/javax/annotations/jsr-250-api/1.0/jsr250-api-1.0.pom > please upload JSR-250 (javax.annotations) 1.0 final POM > --- > > Key: MAVENUPLOAD-1543 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1543 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: nicolas de loof > > JSR 250 commons java annotations has been voted 1.0 final on 11 May, 2006 -- 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-2166) Provide the help listing as default when no arguments are provided
[ http://jira.codehaus.org/browse/MNG-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95903 ] Stefano Bagnara commented on MNG-2166: -- I was just adding a similar bug report. Having at least an informative "mvn help" would really help. I keep adding "BUILDING.txt" files to my projects to tell people what mvn commands they have to use to create the site, to create the package, to run some other plugin I configured in specific profiles and so on. Even a simple plugin (maven-help-plugin) that answer by default a text written in the pom would be a big step forward, then having a property for a default target to be invoked (defaulting to the "maven-help-plugin", but possibily overridable with package, site:stage or anything wirtten in the pom) would be a great solution (similar to what we had in ant) this "maven-help-plugin" could support inline text or a reference to a file to be shown or any other more advanced feature (automatically output help for the more common goals). > Provide the help listing as default when no arguments are provided > -- > > Key: MNG-2166 > URL: http://jira.codehaus.org/browse/MNG-2166 > Project: Maven 2 > Issue Type: New Feature > Components: Command Line >Affects Versions: 2.0, 2.0.1, 2.0.2 > Environment: Any >Reporter: Andre Ranvik >Priority: Minor > Fix For: 2.2.x > > > When just writing "mvn" with no arguments on the command line I get a message > such as this: > >mvn > [INFO] Scanning for projects... > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] You must specify at least one goal. Try 'install' > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Wed Mar 22 09:15:04 CET 2006 > [INFO] Final Memory: 1M/2M > [INFO] > > Many new users to maven or any other such tools are used to getting at least > some basic info of what is expected. How about just displaying the listing > that shows up when a user writes "mvn -h" as default when no arguments are > privided? This is also a feature that most other similar products have. I > also would suggest printing a URL for where they can get basic information > for how to use maven. -- 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: (MRM-342) Incorrect cron expressions in default-archiva.xml
Incorrect cron expressions in default-archiva.xml - Key: MRM-342 URL: http://jira.codehaus.org/browse/MRM-342 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Fabrice BELLINGARD Priority: Minor Attachments: default-archiva.xml.patch This results in a "ParseException" when the application starts, which disables the repository scanning. I attached a patch with valid cron expressions. -- 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: (MRM-342) Incorrect cron expressions in default-archiva.xml
[ http://jira.codehaus.org/browse/MRM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrice BELLINGARD closed MRM-342. -- Resolution: Duplicate Ooops, I've just seen that Arnaud had already reported this bug (MRM-306) > Incorrect cron expressions in default-archiva.xml > - > > Key: MRM-342 > URL: http://jira.codehaus.org/browse/MRM-342 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Fabrice BELLINGARD >Priority: Minor > Attachments: default-archiva.xml.patch > > > This results in a "ParseException" when the application starts, which > disables the repository scanning. > I attached a patch with valid cron expressions. -- 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: (MRM-306) The default Cron expression is invalid
[ http://jira.codehaus.org/browse/MRM-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95912 ] Fabrice BELLINGARD commented on MRM-306: I had put a patch in the duplicate issue MRM-342. > The default Cron expression is invalid > -- > > Key: MRM-306 > URL: http://jira.codehaus.org/browse/MRM-306 > Project: Archiva > Issue Type: Bug > Components: scheduling, web application >Affects Versions: 1.0-alpha-1 >Reporter: Arnaud Heritier > Fix For: 1.0-alpha-1 > > > The default cron expression is invalid when when you setup archiva. You have > to add the * in the year field. -- 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-1544) Upload Stripes 1.4.3 to IBiblio Repository
Upload Stripes 1.4.3 to IBiblio Repository -- Key: MAVENUPLOAD-1544 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1544 Project: maven-upload-requests Issue Type: Task Reporter: Tim Fennell Please upload the Stripes 1.4.3 bundle to the IBiblio repository -- 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: (MRM-306) The default Cron expression is invalid
[ http://jira.codehaus.org/browse/MRM-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrice BELLINGARD closed MRM-306. -- Resolution: Fixed Patch applied. > The default Cron expression is invalid > -- > > Key: MRM-306 > URL: http://jira.codehaus.org/browse/MRM-306 > Project: Archiva > Issue Type: Bug > Components: scheduling, web application >Affects Versions: 1.0-alpha-1 >Reporter: Arnaud Heritier >Assignee: Fabrice BELLINGARD > Fix For: 1.0-alpha-1 > > > The default cron expression is invalid when when you setup archiva. You have > to add the * in the year field. -- 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: (MRELEASE-231) Rewriting scm urls when a tagBase parameter is present.
Rewriting scm urls when a tagBase parameter is present.
---
Key: MRELEASE-231
URL: http://jira.codehaus.org/browse/MRELEASE-231
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: scm
Affects Versions: 2.0-beta-5
Reporter: Paul Gier
For example, I have a simple pom like this:
{quote}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.jboss.maven.test
maven-build-test-module1
1.0-SNAPSHOT
Test Project
A project to test the release and packaging features of
maven
scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk
org.apache.maven.plugins
maven-release-plugin
2.0-beta-5
https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags
{quote}
When I prepare a release, the URLs in the scm configuration are translated to
the following:
{quote}
scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
{quote}
The developer connection is correct because it is based off the tagBase, but
the connection and url in this case are now pointing to the wrong place.
Maybe there should be separate release plugin parameters similar to tagBase,
but used for setting the tag urls for scm.connection and scm.url.
--
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: (MRELEASE-231) Rewriting scm urls when a tagBase parameter is present.
[
http://jira.codehaus.org/browse/MRELEASE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95940
]
Paul Gier commented on MRELEASE-231:
One option to improve this issue is to only modify the path after the hostname.
So for
http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk
This part
http://fisheye.jboss.org/
would stay the same, and this part
repos/labs/labs/jbossbuild/maven-build-test/trunk
Could be taken from the tag base.
> Rewriting scm urls when a tagBase parameter is present.
> ---
>
> Key: MRELEASE-231
> URL: http://jira.codehaus.org/browse/MRELEASE-231
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 2.0-beta-5
>Reporter: Paul Gier
>
> For example, I have a simple pom like this:
> {quote}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> org.jboss.maven.test
> maven-build-test-module1
> 1.0-SNAPSHOT
> Test Project
> A project to test the release and packaging features of
> maven
>
>
> scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
>
> http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.0-beta-5
>
>
> https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags
>
>
>
>
>
> {quote}
> When I prepare a release, the URLs in the scm configuration are translated to
> the following:
> {quote}
>
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> {quote}
> The developer connection is correct because it is based off the tagBase, but
> the connection and url in this case are now pointing to the wrong place.
> Maybe there should be separate release plugin parameters similar to tagBase,
> but used for setting the tag urls for scm.connection and scm.url.
--
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: (MECLIPSE-268) [eclipse:rad goal] Make customization of servlet version, jsp version, ... possible through pom configuration
[ http://jira.codehaus.org/browse/MECLIPSE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-268. Resolution: Fixed Fix Version/s: 2.4 done > [eclipse:rad goal] Make customization of servlet version, jsp version, ... > possible through pom configuration > - > > Key: MECLIPSE-268 > URL: http://jira.codehaus.org/browse/MECLIPSE-268 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Environment: IBM RAD 6 >Reporter: Olivier Jacob >Assignee: Arnaud Heritier > Fix For: 2.4 > > > The eclipse:rad goal uses hardcoded values for EJB version, Web/Servlet > version, JSP version, ... It would be interesting that these values could be > configured in the pom.xml part of 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] Closed: (MAVENUPLOAD-1544) Upload Stripes 1.4.3 to IBiblio Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1544. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Stripes 1.4.3 to IBiblio Repository > -- > > Key: MAVENUPLOAD-1544 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1544 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tim Fennell >Assignee: Carlos Sanchez > > Please upload the Stripes 1.4.3 bundle to the IBiblio repository -- 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-257) surefire-report reruns tests
[ http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95966 ] Mike Youngstrom commented on SUREFIRE-257: -- I'm attempting to use report-only but I cannot seem to get maven to only execute "report-only" and not "report". It still executes both report-only and report hence my tests are still being executed again when "report" runs. Any ideas? org.apache.maven.plugins maven-surefire-report-plugin 2.3 report-only > surefire-report reruns tests > > > Key: SUREFIRE-257 > URL: http://jira.codehaus.org/browse/SUREFIRE-257 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > Fix For: 2.4 > > Attachments: MSUREFIREREP-6-patch.txt > > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- 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-1541) lucene-analyzers-2.1.0.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1541. --- Assignee: Carlos Sanchez Resolution: Won't Fix Apache projects must release to apache repo themselves http://www.apache.org/dev/repository-faq.html Ping us if they don't do it after you request it > lucene-analyzers-2.1.0.jar > -- > > Key: MAVENUPLOAD-1541 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1541 > Project: maven-upload-requests > Issue Type: Task >Reporter: Michael Böckling >Assignee: Carlos Sanchez > Attachments: lucene-analyzers-2.1.0.jar, pom.xml > > > Apache Lucene Java -- 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-1540) lucene-core-2.1.0.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1540. --- Assignee: Carlos Sanchez Resolution: Won't Fix Apache projects must release to apache repo themselves http://www.apache.org/dev/repository-faq.html Ping us if they don't do it after you request it > lucene-core-2.1.0.jar > - > > Key: MAVENUPLOAD-1540 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1540 > Project: maven-upload-requests > Issue Type: Task >Reporter: Michael Böckling >Assignee: Carlos Sanchez > Attachments: lucene-core-2.1.0.jar, pom.xml > > > Apache Lucene Java -- 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-1539) Repository Upload: krysalis-jCharts-1.0.0-alpha-1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95969 ] Carlos Sanchez commented on MAVENUPLOAD-1539: - please read instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Repository Upload: krysalis-jCharts-1.0.0-alpha-1 > - > > Key: MAVENUPLOAD-1539 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1539 > Project: maven-upload-requests > Issue Type: Task >Reporter: Michael Böckling > Attachments: krysalis-jCharts-1.0.0-alpha-1.jar, pom.xml, pom.xml > > > jCharts is a 100% Java based charting utility that outputs a variety of > charts. This package has been designed from the ground up by volunteers for > displaying charts via Servlets, JSP's, and Swing apps. First release was in > December 2000. -- 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-1536) Upload of jasypt 1.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1536. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload of jasypt 1.3 > > > Key: MAVENUPLOAD-1536 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1536 > Project: maven-upload-requests > Issue Type: Task >Reporter: Daniel Fernández >Assignee: Carlos Sanchez > > http://www.jasypt.org/jasypt-1.3-bundle.jar > http://www.jasypt.org > http://www.jasypt.org/team.html > Jasypt (Java Simplified Encryption) is a java library which allows the > developer to add basic encryption capabilities to his/her projects with > minimum effort, and without the need of having deep knowledge on how > cryptography 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] Closed: (MAVENUPLOAD-1535) Hibernate Core 3.2.4 GA released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1535. --- Assignee: Carlos Sanchez Resolution: Incomplete > Hibernate Core 3.2.4 GA released > > > Key: MAVENUPLOAD-1535 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1535 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kaj Hejer >Assignee: Carlos Sanchez > > see http://hibernate.org/6.html -- 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-1528) Please upload TestExtensions bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95970 ] Carlos Sanchez commented on MAVENUPLOAD-1528: - i suggest net.sf.testextensions http://maven.apache.org/guides/mini/guide-central-repository-upload.html groupId: it will identify your project uniquely across all projects, so we need to enforce a naming schema. For projects with artifacts already uploaded to the Central Repository it can be equal to the one used previously, but for new projects it has to follow the package name rules, what means that has to be at least as a domain name you control, and you can create as many subgroups as you want. There are a lot of poorly defined package names so you must provide proof that you control the domain that matches the groupId. Provide proof means that the project is hosted at that domain or it's owned by a member, in that case you must give the link to the registrar database (whois) where the owner is listed and the page in the project web where the owner is associated with the project. eg. If you use a com.sun.xyz package name we expect that the project is hosted at http://xyz.sun.com. Look at More information about package names. Check also the guide about Maven naming conventions Examples: # www.springframework.org -> org.springframework # oness.sf.net -> net.sf.oness > Please upload TestExtensions bundle > --- > > Key: MAVENUPLOAD-1528 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1528 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Christof Lehmann > > The project TestExtensions proviedes access to non public fields and methods. > It is an extensions for writing unit tests and can be uses from JUnit or > TestNG. It is in an early state of development, but it contains all necessary > functions. -- 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-1537) H2 Database Engine 1.0.20070429
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1537. --- Assignee: Carlos Sanchez Resolution: Fixed > H2 Database Engine 1.0.20070429 > --- > > Key: MAVENUPLOAD-1537 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1537 > Project: maven-upload-requests > Issue Type: Task >Reporter: Toshihiro Nakamura >Assignee: Carlos Sanchez > > H2 Database Engine 1.0.20070429 -- 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-1538) xml-apis-1.2.01.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1538. --- Assignee: Carlos Sanchez Resolution: Won't Fix > xml-apis-1.2.01.jar > --- > > Key: MAVENUPLOAD-1538 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1538 > Project: maven-upload-requests > Issue Type: Task >Reporter: Michael Böckling >Assignee: Carlos Sanchez > Attachments: pom.xml, xml-apis-1.2.01.jar > > > An older version of xml-apis. Needed by ICEFaces-1.5.3 which will follow > later on. POM is partially copied from > http://mirrors.ibiblio.org/pub/mirrors/maven2/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.pom. -- 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-1538) xml-apis-1.2.01.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95971 ] Carlos Sanchez commented on MAVENUPLOAD-1538: - Apache projects must release to apache repo themselves http://www.apache.org/dev/repository-faq.html Ping us if they don't do it after you request it And BTW I can't find it in http://archive.apache.org/dist/xml/commons/ > xml-apis-1.2.01.jar > --- > > Key: MAVENUPLOAD-1538 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1538 > Project: maven-upload-requests > Issue Type: Task >Reporter: Michael Böckling > Attachments: pom.xml, xml-apis-1.2.01.jar > > > An older version of xml-apis. Needed by ICEFaces-1.5.3 which will follow > later on. POM is partially copied from > http://mirrors.ibiblio.org/pub/mirrors/maven2/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.pom. -- 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-1542) Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95972 ] Carlos Sanchez commented on MAVENUPLOAD-1542: - artifactId is misspelled > Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio > -- > > Key: MAVENUPLOAD-1542 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1542 > Project: maven-upload-requests > Issue Type: Task >Reporter: Craig Condit > > http://randomcoder.com/projects/maven-uploads/hibernate-commons-annotations-3.3.0.ga-bundle.jar > http://www.hibernate.org/ > Relational Persistence for Java - Annotations support - Common code > JAR is from hibernate-annotations 3.3.0.ga distribution. > Javadoc and source jars were generated from SVN repository at > http://anonsvn.jboss.org/repos/hibernate/tags/annotations_3_3_0_GA/ > See http://jira.codehaus.org/browse/MAVENUPLOAD-1532#action_95799 for why > this is needed. -- 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-1454) Upload of rmock 2.0.0. Group already exists.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1454. --- Resolution: Fixed I think this is fixed now, last slash was missing > Upload of rmock 2.0.0. Group already exists. > > > Key: MAVENUPLOAD-1454 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1454 > Project: maven-upload-requests > Issue Type: Task >Reporter: Daniel Brolund >Assignee: Carlos Sanchez > > 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. -- 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-1542) Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95974 ] Craig Condit commented on MAVENUPLOAD-1542: --- Sorry, missed that. Fixed and uploaded to same URL. > Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio > -- > > Key: MAVENUPLOAD-1542 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1542 > Project: maven-upload-requests > Issue Type: Task >Reporter: Craig Condit > > http://randomcoder.com/projects/maven-uploads/hibernate-commons-annotations-3.3.0.ga-bundle.jar > http://www.hibernate.org/ > Relational Persistence for Java - Annotations support - Common code > JAR is from hibernate-annotations 3.3.0.ga distribution. > Javadoc and source jars were generated from SVN repository at > http://anonsvn.jboss.org/repos/hibernate/tags/annotations_3_3_0_GA/ > See http://jira.codehaus.org/browse/MAVENUPLOAD-1532#action_95799 for why > this is needed. -- 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-1545) JexcelAPI 2.6.3 Upload
JexcelAPI 2.6.3 Upload -- Key: MAVENUPLOAD-1545 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1545 Project: maven-upload-requests Issue Type: Task Reporter: Kevin Conaway Attachments: jxl-2.6.3-bundle.jar I am not a developer of this project. The repository bundle is attached. The administrators of this project do not care to move to Maven but we depend on this project. The project URL is: http://jexcelapi.sourceforge.net Alternatively, please install the latest version from here: http://sourceforge.net/project/showfiles.php?group_id=79926 Thanks, Kevin -- 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-45) Excluded files should be added to compiled sources
[ http://jira.codehaus.org/browse/MCLOVER-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95976 ] Mike Youngstrom commented on MCLOVER-45: It appears now that if I "include" only specific files and don't exclude any then only the included files are being copied over and not any of the files that I didn't include. > Excluded files should be added to compiled sources > --- > > Key: MCLOVER-45 > URL: http://jira.codehaus.org/browse/MCLOVER-45 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Henrik Mejlgaard >Assignee: Vincent Massol > Fix For: 2.4 > > > When excluding files, these are not included in the compiled sources and > therefor gives an compile error as the excluded files cannot be found. > My proposed fix would be to collect and copy the excluded source files to an > excluded_src folder in the target/clover directory, which then could be added > to the compiled sources list. -- 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-1526) Sync jXLS repository to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1526. --- Assignee: Carlos Sanchez Resolution: Fixed You were missing a slash in the script > Sync jXLS repository to the central repository > -- > > Key: MAVENUPLOAD-1526 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1526 > Project: maven-upload-requests > Issue Type: Task >Reporter: Leonid Vysochyn >Assignee: Carlos Sanchez > Attachments: net.sf.jxls.sh > > > Please do a sync of jxls repository > /home/groups/j/jx/jxls/htdocs/repository/releases to central repository as > there is a new release of jXLS library (0.9.3) -- 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: (MRELEASE-231) Rewriting scm urls when a tagBase parameter is present.
[
http://jira.codehaus.org/browse/MRELEASE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MRELEASE-231:
---
Attachment: maven-release-manager.patch
Patch file contains changes to determine the relative url between the trunk and
the tag. This relative url is then used for determining what the tag scm.url
and scm.connection should be.
The patch also includes a new unit test to verify the new functionality.
> Rewriting scm urls when a tagBase parameter is present.
> ---
>
> Key: MRELEASE-231
> URL: http://jira.codehaus.org/browse/MRELEASE-231
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 2.0-beta-5
>Reporter: Paul Gier
> Attachments: maven-release-manager.patch
>
>
> For example, I have a simple pom like this:
> {quote}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> org.jboss.maven.test
> maven-build-test-module1
> 1.0-SNAPSHOT
> Test Project
> A project to test the release and packaging features of
> maven
>
>
> scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/
>
> http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 2.0-beta-5
>
>
> https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags
>
>
>
>
>
> {quote}
> When I prepare a release, the URLs in the scm configuration are translated to
> the following:
> {quote}
>
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0
>
> {quote}
> The developer connection is correct because it is based off the tagBase, but
> the connection and url in this case are now pointing to the wrong place.
> Maybe there should be separate release plugin parameters similar to tagBase,
> but used for setting the tag urls for scm.connection and scm.url.
--
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-2854) Recreating pom.properties always breaks the archivers uptodate check
[
http://jira.codehaus.org/browse/MNG-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95979
]
Carlos Sanchez commented on MNG-2854:
-
Please add the apache license to PomPropertiesUtil.java if you grant the
license to the ASF
> Recreating pom.properties always breaks the archivers uptodate check
>
>
> Key: MNG-2854
> URL: http://jira.codehaus.org/browse/MNG-2854
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.5
>Reporter: Jochen Wiedmann
> Attachments: maven-archiver-properties-2.patch,
> maven-archiver-properties-3.patch, maven-archiver-properties.patch
>
>
> The maven-archiver creates a file called pom.properties on every invocation.
> (Unless the flag "addMavenDescriptor" is set to false, which few people do.)
> This forced recreation makes the uptodate check fail. In other words, jar
> files are always recreated, regardless whether anything was recompiled.
> Obviously, this makes the uptodate check of war files etc. fail as well,
> because the included jar files are always changed.. This is a major drawback,
> because it makes Maven much slower than, for example, Ant-.
> The attached patch proposes a solution for the same problem. What the patch
> does:
> - It is obviously bad, that the generated pom.properties file is in the
> projects directory. The
> patch moves the file to ${project.build.directory}/maven-archiver, which
> seems to me to
> be a more sensible solution.
> - Second, whether we like it or not, there are projects, which create
> multiple artifacts. In other
> words, it isn't good to have a single file. The patch renames the
> pom.properties file to
> ${groupId}/$artifactFinalName.properties. Hopefully, this is sufficiently
> unique.
> - Finally, the patch makes the maven-archiver check, whether the
> pom.properties file has
> actually changed. (In other words, whether groupId, artifactId, or version
> have changed.)
> It does so, by writing the file to an internal buffer and comparing the
> file on the disk and
> the internal buffer (after skipping the line with the timestamp).
> In other words, in the usual case, where groupId, artifactId and version
> haven't changed, the pom.properties file remains unchanged. In particular,
> the jar file doesn't need to be recreated.
--
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-2854) Recreating pom.properties always breaks the archivers uptodate check
[
http://jira.codehaus.org/browse/MNG-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann updated MNG-2854:
-
Attachment: maven-archiver-MNG2854-4.patch
Done.
> Recreating pom.properties always breaks the archivers uptodate check
>
>
> Key: MNG-2854
> URL: http://jira.codehaus.org/browse/MNG-2854
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.5
>Reporter: Jochen Wiedmann
> Attachments: maven-archiver-MNG2854-4.patch,
> maven-archiver-properties-2.patch, maven-archiver-properties-3.patch,
> maven-archiver-properties.patch
>
>
> The maven-archiver creates a file called pom.properties on every invocation.
> (Unless the flag "addMavenDescriptor" is set to false, which few people do.)
> This forced recreation makes the uptodate check fail. In other words, jar
> files are always recreated, regardless whether anything was recompiled.
> Obviously, this makes the uptodate check of war files etc. fail as well,
> because the included jar files are always changed.. This is a major drawback,
> because it makes Maven much slower than, for example, Ant-.
> The attached patch proposes a solution for the same problem. What the patch
> does:
> - It is obviously bad, that the generated pom.properties file is in the
> projects directory. The
> patch moves the file to ${project.build.directory}/maven-archiver, which
> seems to me to
> be a more sensible solution.
> - Second, whether we like it or not, there are projects, which create
> multiple artifacts. In other
> words, it isn't good to have a single file. The patch renames the
> pom.properties file to
> ${groupId}/$artifactFinalName.properties. Hopefully, this is sufficiently
> unique.
> - Finally, the patch makes the maven-archiver check, whether the
> pom.properties file has
> actually changed. (In other words, whether groupId, artifactId, or version
> have changed.)
> It does so, by writing the file to an internal buffer and comparing the
> file on the disk and
> the internal buffer (after skipping the line with the timestamp).
> In other words, in the usual case, where groupId, artifactId and version
> haven't changed, the pom.properties file remains unchanged. In particular,
> the jar file doesn't need to be recreated.
--
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: (MNG-2854) Recreating pom.properties always breaks the archivers uptodate check
[
http://jira.codehaus.org/browse/MNG-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MNG-2854.
---
Assignee: Carlos Sanchez
Resolution: Fixed
Applied in 2.3-SNAPSHOT
> Recreating pom.properties always breaks the archivers uptodate check
>
>
> Key: MNG-2854
> URL: http://jira.codehaus.org/browse/MNG-2854
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.5
>Reporter: Jochen Wiedmann
>Assignee: Carlos Sanchez
> Attachments: maven-archiver-MNG2854-4.patch,
> maven-archiver-properties-2.patch, maven-archiver-properties-3.patch,
> maven-archiver-properties.patch
>
>
> The maven-archiver creates a file called pom.properties on every invocation.
> (Unless the flag "addMavenDescriptor" is set to false, which few people do.)
> This forced recreation makes the uptodate check fail. In other words, jar
> files are always recreated, regardless whether anything was recompiled.
> Obviously, this makes the uptodate check of war files etc. fail as well,
> because the included jar files are always changed.. This is a major drawback,
> because it makes Maven much slower than, for example, Ant-.
> The attached patch proposes a solution for the same problem. What the patch
> does:
> - It is obviously bad, that the generated pom.properties file is in the
> projects directory. The
> patch moves the file to ${project.build.directory}/maven-archiver, which
> seems to me to
> be a more sensible solution.
> - Second, whether we like it or not, there are projects, which create
> multiple artifacts. In other
> words, it isn't good to have a single file. The patch renames the
> pom.properties file to
> ${groupId}/$artifactFinalName.properties. Hopefully, this is sufficiently
> unique.
> - Finally, the patch makes the maven-archiver check, whether the
> pom.properties file has
> actually changed. (In other words, whether groupId, artifactId, or version
> have changed.)
> It does so, by writing the file to an internal buffer and comparing the
> file on the disk and
> the internal buffer (after skipping the line with the timestamp).
> In other words, in the usual case, where groupId, artifactId and version
> haven't changed, the pom.properties file remains unchanged. In particular,
> the jar file doesn't need to be recreated.
--
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: (MWAR-102) Upgrade maven-archiver dependency to 2.3-SNAPSHOT
Upgrade maven-archiver dependency to 2.3-SNAPSHOT - Key: MWAR-102 URL: http://jira.codehaus.org/browse/MWAR-102 Project: Maven 2.x War Plugin Issue Type: Improvement Reporter: Jochen Wiedmann Making use of MNG-2854 should increase the plugins performance. -- 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: (MJAR-56) maven-jar-plugin: Update site documentation from sources
[ http://jira.codehaus.org/browse/MJAR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95982 ] Jochen Wiedmann commented on MJAR-56: - The site was updated at 2006-Nov-15. This issue can most likely be closed. > maven-jar-plugin: Update site documentation from sources > > > Key: MJAR-56 > URL: http://jira.codehaus.org/browse/MJAR-56 > Project: Maven 2.x Jar Plugin > Issue Type: Task >Reporter: Marcel May >Priority: Minor > > Please update the maven plugin documentation at > http://maven.apache.org/plugins/maven-jar-plugin/ for the maven jar plugin, > it's quire out of date (Last Published: Sun Oct 16 04:42:06 EST 2005). > Currently contains dead links, too (eg Project Info/Source Repository/Web > Access). > Possibly applies to many other plugins, too. > Sorry if this is not the correct way to trigger a plugin site update ... ? > Thx alot! -- 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: (MJAR-74) Upgrade maven-archiver dependency to 2.3-SNAPSHOT
Upgrade maven-archiver dependency to 2.3-SNAPSHOT - Key: MJAR-74 URL: http://jira.codehaus.org/browse/MJAR-74 Project: Maven 2.x Jar Plugin Issue Type: Improvement Reporter: Jochen Wiedmann Making use of MNG-2854 should increase the plugins performance. -- 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-1543) please upload JSR-250 (javax.annotations) 1.0 final POM
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1543. --- Assignee: Carlos Sanchez Resolution: Fixed Uploaded with jars from glassfish http://download.java.net/maven/1/javax.annotation/jars/ hopefully they are the right ones > please upload JSR-250 (javax.annotations) 1.0 final POM > --- > > Key: MAVENUPLOAD-1543 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1543 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: nicolas de loof >Assignee: Carlos Sanchez > > JSR 250 commons java annotations has been voted 1.0 final on 11 May, 2006 -- 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-1542) Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1542. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga to ibiblio > -- > > Key: MAVENUPLOAD-1542 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1542 > Project: maven-upload-requests > Issue Type: Task >Reporter: Craig Condit >Assignee: Carlos Sanchez > > http://randomcoder.com/projects/maven-uploads/hibernate-commons-annotations-3.3.0.ga-bundle.jar > http://www.hibernate.org/ > Relational Persistence for Java - Annotations support - Common code > JAR is from hibernate-annotations 3.3.0.ga distribution. > Javadoc and source jars were generated from SVN repository at > http://anonsvn.jboss.org/repos/hibernate/tags/annotations_3_3_0_GA/ > See http://jira.codehaus.org/browse/MAVENUPLOAD-1532#action_95799 for why > this is needed. -- 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-1545) JexcelAPI 2.6.3 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95986 ] Carlos Sanchez commented on MAVENUPLOAD-1545: - previous versions are under net.sourceforge.jexcelapi please change and if there's no scm just comment it out saying it's not available > JexcelAPI 2.6.3 Upload > -- > > Key: MAVENUPLOAD-1545 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1545 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevin Conaway > Attachments: jxl-2.6.3-bundle.jar > > > I am not a developer of this project. The repository bundle is attached. > The administrators of this project do not care to move to Maven but we depend > on this project. > The project URL is: > http://jexcelapi.sourceforge.net > Alternatively, please install the latest version from here: > http://sourceforge.net/project/showfiles.php?group_id=79926 > Thanks, > Kevin -- 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-1545) JexcelAPI 2.6.3 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95988 ] Kevin Conaway commented on MAVENUPLOAD-1545: Hi Carlos, I've fixed the groupId. If I leave the scm element out of the POM, the repository command fails. Is net.sourceforge.jexcelapi the correct groupId going forward? There is also a build under the groupId jexcelapi that should probably be removed. Kevin > JexcelAPI 2.6.3 Upload > -- > > Key: MAVENUPLOAD-1545 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1545 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevin Conaway > Attachments: jxl-2.6.3-bundle.jar, jxl-2.6.3-bundle.jar > > > I am not a developer of this project. The repository bundle is attached. > The administrators of this project do not care to move to Maven but we depend > on this project. > The project URL is: > http://jexcelapi.sourceforge.net > Alternatively, please install the latest version from here: > http://sourceforge.net/project/showfiles.php?group_id=79926 > Thanks, > Kevin -- 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: (MAVENUPLOAD-1545) JexcelAPI 2.6.3 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Conaway updated MAVENUPLOAD-1545: --- Attachment: jxl-2.6.3-bundle.jar Fixed with the correct groupId. > JexcelAPI 2.6.3 Upload > -- > > Key: MAVENUPLOAD-1545 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1545 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevin Conaway > Attachments: jxl-2.6.3-bundle.jar, jxl-2.6.3-bundle.jar > > > I am not a developer of this project. The repository bundle is attached. > The administrators of this project do not care to move to Maven but we depend > on this project. > The project URL is: > http://jexcelapi.sourceforge.net > Alternatively, please install the latest version from here: > http://sourceforge.net/project/showfiles.php?group_id=79926 > Thanks, > Kevin -- 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-1546) Version 1.4 of UISPec4J
Version 1.4 of UISPec4J --- Key: MAVENUPLOAD-1546 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1546 Project: maven-upload-requests Issue Type: New Feature Reporter: Pascal Pratmarty Attachments: uispec4j-1.4-bundle.jar UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness. -- 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: (MRM-343) configurationInterceptor intercepts /admin/addRepository so one cannot add repository
configurationInterceptor intercepts /admin/addRepository so one cannot add repository - Key: MRM-343 URL: http://jira.codehaus.org/browse/MRM-343 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1 Environment: Windows XP Reporter: Roman Kalukiewicz Priority: Blocker Fresh installation started from plexus (fresh build archiva-1.0-alpha-1-SNAPSHOT-bin.tar.gz) creates new admin user, but when he logs in, browser informs, that circular redirect occurs. The only way to solve this problem is to restart archiva. This way you can see repositories, but there is no ArchivaRoleConstants.OPERATION_REPOSITORY_ACCESS permission created for internal and snapshot repositories, so no one (even admin) can access repository by WebDAV. -- 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: (MRM-344) no /WEB-INF/jsp/admin/deleteProxyConnector.jsp required by action deleteProxyConnector
no /WEB-INF/jsp/admin/deleteProxyConnector.jsp required by action deleteProxyConnector -- Key: MRM-344 URL: http://jira.codehaus.org/browse/MRM-344 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1 Reporter: Roman Kalukiewicz there is nothing to add - this function simply doesn't work now :( -- 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-257) surefire-report reruns tests
[ http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95989 ] Barrie Treloar commented on SUREFIRE-257: - This is because 2.4 has not been released yet, so unless you have build a local copy and installed it report-only is not available yet. > surefire-report reruns tests > > > Key: SUREFIRE-257 > URL: http://jira.codehaus.org/browse/SUREFIRE-257 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > Fix For: 2.4 > > Attachments: MSUREFIREREP-6-patch.txt > > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- 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-70) Non-Clovered Jars used for Transitive Dependencies
[ http://jira.codehaus.org/browse/MCLOVER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gredler updated MCLOVER-70: -- Attachment: mclover-70.patch We've run into this issue as well, but it's not so much that transitive dependencies don't get clovered -- the problem is that both clovered and unclovered dependencies get used, meaning some transitive dependencies get their coverage updated, while others don't. The Clover plugin "clovers" all dependencies (including transitive ones) correctly in CloverInstrumentInternalMojo#swizzleCloverDependencies(), but during the transitive dependency resolution which occurs later, Maven correctly recognizes that the regular versions of the clovered transitive dependencies are no longer referenced, and adds them. The result is that both versions of the transitive dependencies get referenced, and sometimes one version gets used, sometimes the other. I'm attaching a patch which has fixed the problem for us locally. All it does is wrap clovered artifacts in a special Artifact implementation which delegates equals(), hashCode() and getDependencyConflictId() to a non-clovered artifact, so that during transitive dependency resolution the clovered artifact "looks" like the non-clovered version. > Non-Clovered Jars used for Transitive Dependencies > -- > > Key: MCLOVER-70 > URL: http://jira.codehaus.org/browse/MCLOVER-70 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: James Olsen > Attachments: mclover-70.patch > > > When executing tests or building ear/war archives, the plugin is not using > instrumented jars for transitive dependencies. The ordinary jar is used > instead. Hence no test coverage stats are obtained for those components. > Adding the transitive dependency as a direct dependency on the project > results in both the instrumented and plain jar appearing in the archive. I > presume the same also happens for the unit test classpath although I haven't > confirmed. > The plugin should use the instrumented version of the jar where available > regardless of whether the dependency is direct or transitive. -- 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-157) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method
[
http://jira.codehaus.org/browse/SUREFIRE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95992
]
Ian Springer commented on SUREFIRE-157:
---
This issue also exists for methods annotated with @BeforeSuite.
> Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest
> method
> ---
>
> Key: SUREFIRE-157
> URL: http://jira.codehaus.org/browse/SUREFIRE-157
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Windows XP, JDK 1.5, Maven 2.0.4, TestNG 5.1
>Reporter: Manish Shah
> Fix For: 2.4
>
>
> Create a TestNG test with a method as follows:
> @BeforeTest
> public void beforeTest() {
> throw new RuntimeException("Simulate an exception from a beforeTest
> method");
> }
> When surefire attempts to run this test, the plugin fails with the following
> stack trace:
> org.apache.maven.surefire.booter.SurefireExecutionException: null; nested
> exception is java.lang.NullPointerException: n
> ull
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.report.AbstractTextReporter.testFailed(AbstractTextReporter.java:106)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:299)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:281)
> at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:97)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1164)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1149)
> at
> org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:191)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:170)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:236)
> at org.testng.SuiteRunner.run(SuiteRunner.java:145)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:863)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:64)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
--
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: (MIDEA-93) Allow user to specify IntelliJ module name that is generated
Allow user to specify IntelliJ module name that is generated
Key: MIDEA-93
URL: http://jira.codehaus.org/browse/MIDEA-93
Project: Maven 2.x IDEA Plugin
Issue Type: New Feature
Affects Versions: 2.0
Reporter: ronn chinowutthichai
Priority: Critical
In reference to this mail thread -
http://www.nabble.com/Specifying-IntelliJ-module-name-with-maven-idea-plugin-tf3756364s177.html
Currently IntelliJ module name that is generated is derived solely from
artifactId.
IntelliJ module name has to be unique within a project and this can cause
conflict when maven project structure has several sub modules of the same name.
i.e.,
project/
+- common/webapp/
+- customer/webapp/
I'm proposing that
a) the default module name should be derived from pom's project name (rather
than artifactId). (as I understand it the project name is merely used for
console log display and it would make sense for user to make it unique within
his/her project structure).
b) that the plugin should provide a configuration parameter to override this
default behaviour.
Currently I have hacked the plugin to use ${groupId}.${artifactId} as the
generated IntelliJ module name. I can do abit more work to provide a patch if
needed.
--
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
