[jira] Created: (MAVENUPLOAD-1683) Upload jython-2.2
Upload jython-2.2 - Key: MAVENUPLOAD-1683 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1683 Project: maven-upload-requests Issue Type: Task Reporter: Charlie Groves -- 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-255) during a release several elements are removed from the pom.xml (which should be left there)
[ http://jira.codehaus.org/browse/MRELEASE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105611 ] Carsten Ziegeler commented on MRELEASE-255: --- I can confirm that this is still a bug - under specific circumstances the plugin removes everything before the first xml element (the intro and outro parts). After some testing, I found some problems: the main problem is that the pom is parsed into a dom and then compared with a string version to detect the intro and outro parts. If the underlying dom implementation or the serialization from the dom to a string is altering only one single character the comparison will fail, and intro and outro is removed! One problem I noticed are the namespace and schema definitions: If I have the following in my pom: 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";> everything before is removed, if I use 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";> (everything in one line and specific order) it works! Imho, the current approach should be replaced with an approach which just replaces the changing elements in the pom, like a sax based approach which detects the locations and just changes them on the fly. A very simple approach would be to use an xslt stylesheet for this: it can match on the elements to change and just copy everything else. If you need help in such a solution, let me know. > during a release several elements are removed from the pom.xml (which should > be left there) > --- > > Key: MRELEASE-255 > URL: http://jira.codehaus.org/browse/MRELEASE-255 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Roman Cerny > > the following elements are removed from the pom.xml, during a 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] Commented: (MNG-401) Add meta-data to root of Maven repository.
[ http://jira.codehaus.org/browse/MNG-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105612 ] Carlos Sanchez commented on MNG-401: Also some people suggested adding the permissions there instead of the client settings file > Add meta-data to root of Maven repository. > -- > > Key: MNG-401 > URL: http://jira.codehaus.org/browse/MNG-401 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories > Environment: N/A >Reporter: Faron Dutton > Fix For: 2.1.x > > > Add an XML file (e.g., maven-info.xml) to the root of all Maven repositories > that describes which variant of the repository structure a site uses. This > would be very helpful for tools that need to navigate a repository's > directory structure. For repositories that lack this meta-data, the tool > would assume a Maven 1.0 structure. -- 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_105613 ] Fabrice BELLINGARD commented on SUREFIRE-257: - The goal "report-only" actually exists in version 2.3, but when you launch a "mvn install site", you can see that the tests get executed twice. Which is a bug. This bug is fixed in SVN. So if you use version 2.3.1-SNAPSHOT, this works perfectly. > 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] Created: (MNG-3164) Enable plugin configuration in settings.xml
Enable plugin configuration in settings.xml --- Key: MNG-3164 URL: http://jira.codehaus.org/browse/MNG-3164 Project: Maven 2 Issue Type: New Feature Components: Settings Reporter: Petr Kozelka Currently there is no way to correctly persist user-specific configuration of plugins. There are many plugins, that do not affect the build process, and should therefore NOT be configured in pom.xml (and versioned and released etc). This is most annoying with IDE integration plugins. In a team, some developers use IDEA, some Eclipse, some Netbeans or anything else. It is apparently a nonsense to preconfigure anything about IDEA in pom.xml and commit it to the repository, because others either do not care or perhaps want different settings. Ideally, it should be part of profile section. And to make the things really correct, each plugin (or even parameter?) should specify whether it can be configured in pom only, in settings only, or in both; one of these options might be used as the default. This feature will greatly improve the pom's reputation of being a project descriptor, instead of being one user's setup. -- 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-1683) Upload jython-2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1683. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload jython-2.2 > - > > Key: MAVENUPLOAD-1683 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1683 > Project: maven-upload-requests > Issue Type: Task >Reporter: Charlie Groves >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-1681) java exchange connector (jec-1.53_11.jar)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1681. --- Assignee: Carlos Sanchez Resolution: Fixed > java exchange connector (jec-1.53_11.jar) > - > > Key: MAVENUPLOAD-1681 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1681 > Project: maven-upload-requests > Issue Type: Wish >Reporter: eli hasson >Assignee: Carlos Sanchez > > java exchange connector is a pure java api for Microsoft exchange server. > for more information: > [EMAIL PROTECTED] -- 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-1682) rhino-js-1.6R7 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105616 ] Carlos Sanchez commented on MAVENUPLOAD-1682: - jar xf js-1.6R7-bundle.jar java.util.zip.ZipException: invalid entry CRC (expected 0x7d1a582d but got 0xc289cba0) at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:378) at java.util.zip.ZipInputStream.read(ZipInputStream.java:141) at sun.tools.jar.Main.extractFile(Main.java:714) at sun.tools.jar.Main.extract(Main.java:677) at sun.tools.jar.Main.run(Main.java:189) at sun.tools.jar.Main.main(Main.java:903) > rhino-js-1.6R7 upload request > - > > Key: MAVENUPLOAD-1682 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1682 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ahmed Ashour > > Downloaded from http://www.mozilla.org/rhino/download.html > New features in 1.6R7 can be found at > http://developer.mozilla.org/en/docs/New_in_Rhino_1.6R7 -- 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-2808) Anchors on maven.apache.org are broken
[ http://jira.codehaus.org/browse/MNG-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105622 ] Petr Kozelka commented on MNG-2808: --- now it seems to be fixed, as far as I could check > Anchors on maven.apache.org are broken > -- > > Key: MNG-2808 > URL: http://jira.codehaus.org/browse/MNG-2808 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting > Environment: Both Firefox 2 and IE 7.0 >Reporter: Alexander Dotor >Priority: Minor > Fix For: Reviewed Pending Version Assignment > > > The anchors for on-page-navigation on maven.apache.org are broken. The > href-attrivbute contains uppercase letters at the beginning and blanks > between words. The name-Attribute of the appropriate anchors is in lowercase > and containts underscores instead of blanks. > This makes it extremly difficult to navigate the POM-Reference for example. -- 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: (MEV-544) batik-rasterizer-ext has incorrect artifact id
[ http://jira.codehaus.org/browse/MEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105623 ] Henri Yandell commented on MEV-544: --- This seems like one that should be fixed, rather than asking for a new release. Anyone think otherwise? > batik-rasterizer-ext has incorrect artifact id > -- > > Key: MEV-544 > URL: http://jira.codehaus.org/browse/MEV-544 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Mark Hobson > > Artifact id is "batik-rasterizer" and not "batik-rasterizer-ext": > ftp://ibiblio.org/pub/packages/maven2/batik/batik-rasterizer-ext/1.6-1/batik-rasterizer-ext-1.6-1.pom > Thus creating a circular dependency within itself and confusion with: > ftp://ibiblio.org/pub/packages/maven2/batik/batik-rasterizer/1.6-1/batik-rasterizer-1.6-1.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: (MEV-536) Broken checksums and signature for maven-2.0.7.pom
[ http://jira.codehaus.org/browse/MEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105624 ] Henri Yandell commented on MEV-536: --- I've modified it in the ASF repository. It should sync over. I'll leave this issue open and check again later before closing. > Broken checksums and signature for maven-2.0.7.pom > -- > > Key: MEV-536 > URL: http://jira.codehaus.org/browse/MEV-536 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Max Bowsher >Assignee: Henri Yandell > > http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.7/maven-2.0.7.pom > .md5 and .sha1 are broken due to being in incorrect format (generated by BSD > checksum tools?) > .asc is bad signature. -- 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: (MEV-530) Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom
[ http://jira.codehaus.org/browse/MEV-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105625 ] Henri Yandell commented on MEV-530: --- I'm leaving this one to Jason as the RM. I don't want to be generating new sigs claiming that the pom.xml is good without being able to tell if the pom.xml is good. > Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom > > > Key: MEV-530 > URL: http://jira.codehaus.org/browse/MEV-530 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Max Bowsher >Assignee: Jason van Zyl > > org/apache/maven/maven/2.0.6/maven-2.0.6.pom has bad md5 and sha1 -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Gagne updated MEAR-52: -- Attachment: maven-ear-plugin_datasource-patch.txt Here is the patch I have created that Tom Cort mentioned. Let us know what you think, or if there are any changes that should be made! > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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: (MEV-364) Fix dependencies of common-lang 1.0 (add test scope for junit)
[ http://jira.codehaus.org/browse/MEV-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MEV-364. - Resolution: Won't Fix Commons CLI 1.1 is released now and as it lacks dependencies will not exhibit this issue. > Fix dependencies of common-lang 1.0 (add test scope for junit) > -- > > Key: MEV-364 > URL: http://jira.codehaus.org/browse/MEV-364 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies, Invalid POM >Reporter: Guillaume Boissier >Assignee: Henri Yandell > > consider changing > > > junit > junit > 3.7 > > > to > > > junit > junit > 3.7 > test > > -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105628 ] Stephane Nicoll commented on MEAR-52: - I'm sorry Matthew, I will have to reject this. Please *read* the comments in this issue. The only way to do this is to update the jboss-app.xml. I won't create a new module for that and I won't put this information in the application.xml since it's JBoss specific. See also the answer we got from Adrian. The only thing we need is a new option to the JBoss config and an update of the JbossAppXmlWriter. Regards, Stéphane > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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-1582) please upload IBM MQSeries POM
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105629 ] Henri Yandell commented on MAVENUPLOAD-1582: Carlos? Does Nicolas' reply resolve your questions? > please upload IBM MQSeries POM > -- > > Key: MAVENUPLOAD-1582 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1582 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: nicolas de loof > > I'm using those POMs to package IBM MQ series in my apps. > The bundle contains POMs for com.ibm.mq, com.ibm.mqbind and com.ibm.mqjms > JARS, and jar checksums. > Dependencies are discovered based on the MQClient installation /lib and the > code samples (.bat) -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Gagne updated MEAR-52: -- Attachment: maven-ear-plugin_datasource-patch.txt Fixed format/License > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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-1405) Eclipse SWT version 3.2.1 linux
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MAVENUPLOAD-1405. -- Resolution: Won't Fix Carlos' comment implies that this will get done as part of different work. > Eclipse SWT version 3.2.1 linux > > > Key: MAVENUPLOAD-1405 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1405 > Project: maven-upload-requests > Issue Type: Task >Reporter: Demchenko Vitaliy Victorovich > > SWT Eclipse version 3.2.1 for linux -- 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-1552) Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MAVENUPLOAD-1552. -- Resolution: Won't Fix Closing as WONTFIX as it looks like you need to hassle Mark as he owns this. > Upload mysql:mysql-connector-java:jar:5.0.6 to ibiblio > -- > > Key: MAVENUPLOAD-1552 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1552 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/mysql-connector-java-5.0.6-bundle.jar > http://dev.mysql.com/downloads/connector/j/5.0.html > MySQL Connector/J is the official JDBC driver for MySQL. -- 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-1582) please upload IBM MQSeries POM
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105637 ] Carlos Sanchez commented on MAVENUPLOAD-1582: - I think poms can be uploaded > please upload IBM MQSeries POM > -- > > Key: MAVENUPLOAD-1582 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1582 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: nicolas de loof > > I'm using those POMs to package IBM MQ series in my apps. > The bundle contains POMs for com.ibm.mq, com.ibm.mqbind and com.ibm.mqjms > JARS, and jar checksums. > Dependencies are discovered based on the MQClient installation /lib and the > code samples (.bat) -- 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: (MEV-544) batik-rasterizer-ext has incorrect artifact id
[ http://jira.codehaus.org/browse/MEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105635 ] Carlos Sanchez commented on MEV-544: yes, needs to be fixed > batik-rasterizer-ext has incorrect artifact id > -- > > Key: MEV-544 > URL: http://jira.codehaus.org/browse/MEV-544 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Mark Hobson > > Artifact id is "batik-rasterizer" and not "batik-rasterizer-ext": > ftp://ibiblio.org/pub/packages/maven2/batik/batik-rasterizer-ext/1.6-1/batik-rasterizer-ext-1.6-1.pom > Thus creating a circular dependency within itself and confusion with: > ftp://ibiblio.org/pub/packages/maven2/batik/batik-rasterizer/1.6-1/batik-rasterizer-1.6-1.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] Created: (MAVENUPLOAD-1684) jt400-full-6.0-bundle
jt400-full-6.0-bundle - Key: MAVENUPLOAD-1684 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1684 Project: maven-upload-requests Issue Type: Task Reporter: M.H. Avegaart Attachments: jt400-full-5.3-bundle.jar, jt400-full-5.4-bundle.jar https://sourceforge.net/projects/jt400 http://jt400.sourceforge.net/ http://jt400.sourceforge.net/team.html The IBM Toolbox for Java is a library of Java classes supporting the client/server and internet programming models to a system running OS/400 or i5/OS. The classes can be used by Java applets, servlets, and applications to easily access OS/400 and i5/OS data and resources. -- 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-1684) jt400-full-6.0-bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M.H. Avegaart updated MAVENUPLOAD-1684: --- Attachment: jt400-full-5.3-bundle.jar > jt400-full-6.0-bundle > - > > Key: MAVENUPLOAD-1684 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1684 > Project: maven-upload-requests > Issue Type: Task >Reporter: M.H. Avegaart > Attachments: jt400-full-5.3-bundle.jar, jt400-full-5.4-bundle.jar > > > https://sourceforge.net/projects/jt400 > http://jt400.sourceforge.net/ > http://jt400.sourceforge.net/team.html > The IBM Toolbox for Java is a library of Java classes supporting the > client/server and internet programming models to a system running OS/400 or > i5/OS. The classes can be used by Java applets, servlets, and applications to > easily access OS/400 and i5/OS data and resources. -- 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-1684) jt400-full-6.0-bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M.H. Avegaart updated MAVENUPLOAD-1684: --- Attachment: jt400-full-6.0-bundle.jar > jt400-full-6.0-bundle > - > > Key: MAVENUPLOAD-1684 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1684 > Project: maven-upload-requests > Issue Type: Task >Reporter: M.H. Avegaart > Attachments: jt400-full-5.3-bundle.jar, jt400-full-5.4-bundle.jar, > jt400-full-6.0-bundle.jar > > > https://sourceforge.net/projects/jt400 > http://jt400.sourceforge.net/ > http://jt400.sourceforge.net/team.html > The IBM Toolbox for Java is a library of Java classes supporting the > client/server and internet programming models to a system running OS/400 or > i5/OS. The classes can be used by Java applets, servlets, and applications to > easily access OS/400 and i5/OS data and resources. -- 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-1684) jt400-full-6.0-bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M.H. Avegaart updated MAVENUPLOAD-1684: --- Attachment: jt400-full-5.4-bundle.jar > jt400-full-6.0-bundle > - > > Key: MAVENUPLOAD-1684 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1684 > Project: maven-upload-requests > Issue Type: Task >Reporter: M.H. Avegaart > Attachments: jt400-full-5.3-bundle.jar, jt400-full-5.4-bundle.jar > > > https://sourceforge.net/projects/jt400 > http://jt400.sourceforge.net/ > http://jt400.sourceforge.net/team.html > The IBM Toolbox for Java is a library of Java classes supporting the > client/server and internet programming models to a system running OS/400 or > i5/OS. The classes can be used by Java applets, servlets, and applications to > easily access OS/400 and i5/OS data and resources. -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Gagne updated MEAR-52: -- Attachment: maven-ear-plugin_datasource-patch_2.txt Apologies, this new file is the proper patch. > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_2.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Gagne updated MEAR-52: -- Attachment: maven-ear-plugin_datasource-patch_2.txt Here's a patch for an implementation of this feature along the lines that you previously specified. Let me know if this is more acceptable or if there are other changes I should make. > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, maven-ear-plugin_datasource-patch_2.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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-1412) File Inclusion Vulnerability
File Inclusion Vulnerability Key: CONTINUUM-1412 URL: http://jira.codehaus.org/browse/CONTINUUM-1412 Project: Continuum Issue Type: Bug Components: Security Affects Versions: 1.1-beta-2 Environment: Java version: 1.5.0_10 OS name: "linux" version: "2.6.16.49-xen-osl4-ipsec-domu" arch: "i386" Reporter: Tom Cort Priority: Critical Attachments: continuum.JPG The value of the userDirectory variable used when calling workingCopy.action is not filtered properly. This gives anyone who can access workingCopy.action the ability to read any file on the file system with the permissions that jetty is running as. For example, let's say we have continuum installed in /usr/local/continuum. Say we have a project named build-tools with a projectId of 10. Using the following URL, I can display the contents of /proc/version (see attached screenshot). http://some-server.domain.com:8080/continuum/workingCopy.action?projectId=10&projectName=build-tools&userDirectory=../../../../../../../../../proc/&file=version This is really bad if the user is running continuum as root because it gives the attacker access to every file on the file system. -- 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-1682) rhino-js-1.6R7 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105647 ] Ahmed Ashour commented on MAVENUPLOAD-1682: --- Dear Carlos, Sorry for that. It was interrupted upload with no errors. Now it is fine, please try again. > rhino-js-1.6R7 upload request > - > > Key: MAVENUPLOAD-1682 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1682 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ahmed Ashour > > Downloaded from http://www.mozilla.org/rhino/download.html > New features in 1.6R7 can be found at > http://developer.mozilla.org/en/docs/New_in_Rhino_1.6R7 -- 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: (ARCHETYPE-38) The archetype is using user.dir which prohibits clean embedding
[ http://jira.codehaus.org/browse/ARCHETYPE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened ARCHETYPE-38: - Assignee: Carlos Sanchez (was: Kenney Westerhof) > The archetype is using user.dir which prohibits clean embedding > --- > > Key: ARCHETYPE-38 > URL: http://jira.codehaus.org/browse/ARCHETYPE-38 > Project: Maven Archetype > Issue Type: New Feature >Affects Versions: 1.0-alpha-4, 1.0-alpha-5 >Reporter: Philip Dodds >Assignee: Carlos Sanchez > Fix For: 1.0-alpha-5, 1.0-alpha-6 > > Attachments: basedir.patch > > > When using the archetype from an embedded maven (in this case within Eclipse > to create new project templates) the archetype plugin is using the user.dir > as the base for creating the project. If it were to use the basedir you > would be able to re-locate the archetype. > Attached is a patch for maven-archetype-plugin > P -- 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: (ARCHETYPE-38) The archetype is using user.dir which prohibits clean embedding
[ http://jira.codehaus.org/browse/ARCHETYPE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated ARCHETYPE-38: Affects Version/s: 1.0-alpha-4 1.0-alpha-5 Fix Version/s: 1.0-alpha-6 > The archetype is using user.dir which prohibits clean embedding > --- > > Key: ARCHETYPE-38 > URL: http://jira.codehaus.org/browse/ARCHETYPE-38 > Project: Maven Archetype > Issue Type: New Feature >Affects Versions: 1.0-alpha-4, 1.0-alpha-5 >Reporter: Philip Dodds >Assignee: Carlos Sanchez > Fix For: 1.0-alpha-5, 1.0-alpha-6 > > Attachments: basedir.patch > > > When using the archetype from an embedded maven (in this case within Eclipse > to create new project templates) the archetype plugin is using the user.dir > as the base for creating the project. If it were to use the basedir you > would be able to re-locate the archetype. > Attached is a patch for maven-archetype-plugin > P -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Gagne updated MEAR-52: -- Attachment: maven-ear-plugin_datasource-patch_final.txt According to the schema the element cannot have a sub-element in jboss-app.xml... I changed it to generate the data source location with the element and everything works and the data source is found by jboss. I attached the latest version of my code (maven-ear-plugin_datasource-patch_final.txt) with formatting changes to other code removed. >From http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd: "" > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_final.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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: (ARCHETYPE-38) The archetype is using user.dir which prohibits clean embedding
[ http://jira.codehaus.org/browse/ARCHETYPE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated ARCHETYPE-38: Fix Version/s: (was: 1.0-alpha-5) basedir cannot be used as parameter name as it's not injected, I guess conflicting with default basedir property Will change to targetDirectory > The archetype is using user.dir which prohibits clean embedding > --- > > Key: ARCHETYPE-38 > URL: http://jira.codehaus.org/browse/ARCHETYPE-38 > Project: Maven Archetype > Issue Type: New Feature >Affects Versions: 1.0-alpha-4, 1.0-alpha-5 >Reporter: Philip Dodds >Assignee: Carlos Sanchez > Fix For: 1.0-alpha-6 > > Attachments: basedir.patch > > > When using the archetype from an embedded maven (in this case within Eclipse > to create new project templates) the archetype plugin is using the user.dir > as the base for creating the project. If it were to use the basedir you > would be able to re-locate the archetype. > Attached is a patch for maven-archetype-plugin > P -- 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: (MEV-364) Fix dependencies of common-lang 1.0 (add test scope for junit)
[ http://jira.codehaus.org/browse/MEV-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105657 ] Dennis Lundberg commented on MEV-364: - Henri, I agree that this issue should be closed as won't fix. However this issues is for commons-lang to commons-cli. Guillaume, the policy is to not change files in the repository after they have been deployed. This is to make sure that reproducible builds are reproducible. Commons-lang-2.0 has the correct scope set. > Fix dependencies of common-lang 1.0 (add test scope for junit) > -- > > Key: MEV-364 > URL: http://jira.codehaus.org/browse/MEV-364 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies, Invalid POM >Reporter: Guillaume Boissier >Assignee: Henri Yandell > > consider changing > > > junit > junit > 3.7 > > > to > > > junit > junit > 3.7 > test > > -- 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: (MEV-364) Fix dependencies of common-lang 1.0 (add test scope for junit)
[ http://jira.codehaus.org/browse/MEV-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105658 ] Henri Yandell commented on MEV-364: --- Yep. It was being kept open because CLI 1.0 was a known dependency on Lang 1.0. Once CLI 1.1 was released, the importance of the issue was lowered. > Fix dependencies of common-lang 1.0 (add test scope for junit) > -- > > Key: MEV-364 > URL: http://jira.codehaus.org/browse/MEV-364 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies, Invalid POM >Reporter: Guillaume Boissier >Assignee: Henri Yandell > > consider changing > > > junit > junit > 3.7 > > > to > > > junit > junit > 3.7 > test > > -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[
http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105659
]
Stephane Nicoll commented on MEAR-52:
-
come on :)
Who said it should be a Java entry. *read*!
{quote}
According to Adrian Brock, the supported solution is as follows:
So for future compatibility, the correct mechanism for non-spec
deployments is to add a META-INF/jboss-app.xml
mydatasource-ds.xml
{quote}
> Ability to add jboss dataosources (*ds.xml) files as a jarModule
>
>
> Key: MEAR-52
> URL: http://jira.codehaus.org/browse/MEAR-52
> Project: Maven 2.x Ear Plugin
> Issue Type: Wish
>Reporter: Cesar Izurieta
>Assignee: Stephane Nicoll
> Attachments: maven-ear-plugin_datasource-patch.txt,
> maven-ear-plugin_datasource-patch.txt,
> maven-ear-plugin_datasource-patch_2.txt,
> maven-ear-plugin_datasource-patch_2.txt,
> maven-ear-plugin_datasource-patch_final.txt
>
>
> It would be nice to be able to add a jarModule as:
>
>
> mysql-ds.xml
> true
>
>
> So the resulting application.xml looks like:
>
> ...
>
> mysql-ds.xml
>
>
> This would help to deploy jboss datasources with the ear.
--
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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105660 ] Matthew Gagne commented on MEAR-52: --- Yeah, my apologies, I had skimmed that section from Adrian over earlier, but didn't put 2 and 2 together till after my debugging/post. As far as the latest patch, do you think it's up to snuff or is there anything else I should look into fixing? It works on our end for JBoss 4.2.1. -Matt > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_final.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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: (ARCHETYPE-38) The archetype is using user.dir which prohibits clean embedding
[ http://jira.codehaus.org/browse/ARCHETYPE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated ARCHETYPE-38: Comment: was deleted > The archetype is using user.dir which prohibits clean embedding > --- > > Key: ARCHETYPE-38 > URL: http://jira.codehaus.org/browse/ARCHETYPE-38 > Project: Maven Archetype > Issue Type: New Feature >Affects Versions: 1.0-alpha-4, 1.0-alpha-5 >Reporter: Philip Dodds >Assignee: Carlos Sanchez > Fix For: 1.0-alpha-6 > > Attachments: basedir.patch > > > When using the archetype from an embedded maven (in this case within Eclipse > to create new project templates) the archetype plugin is using the user.dir > as the base for creating the project. If it were to use the basedir you > would be able to re-locate the archetype. > Attached is a patch for maven-archetype-plugin > P -- 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: (ARCHETYPE-38) The archetype is using user.dir which prohibits clean embedding
[ http://jira.codehaus.org/browse/ARCHETYPE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed ARCHETYPE-38. --- Resolution: Fixed > The archetype is using user.dir which prohibits clean embedding > --- > > Key: ARCHETYPE-38 > URL: http://jira.codehaus.org/browse/ARCHETYPE-38 > Project: Maven Archetype > Issue Type: New Feature >Affects Versions: 1.0-alpha-4, 1.0-alpha-5 >Reporter: Philip Dodds >Assignee: Carlos Sanchez > Fix For: 1.0-alpha-6 > > Attachments: basedir.patch > > > When using the archetype from an embedded maven (in this case within Eclipse > to create new project templates) the archetype plugin is using the user.dir > as the base for creating the project. If it were to use the basedir you > would be able to re-locate the archetype. > Attached is a patch for maven-archetype-plugin > P -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105661 ] Stephane Nicoll commented on MEAR-52: - Yep it's good I'll apply it. Thanks. > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_final.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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: (MEAR-52) Ability to add jboss dataosources (*ds.xml) files as a jarModule
[ http://jira.codehaus.org/browse/MEAR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-52. --- Resolution: Fixed Fix Version/s: 2.3.2 Applied, thanks even though the patch was impossible to apply (full path) and it had an error in it :) Anyway, I appreciate your help. > Ability to add jboss dataosources (*ds.xml) files as a jarModule > > > Key: MEAR-52 > URL: http://jira.codehaus.org/browse/MEAR-52 > Project: Maven 2.x Ear Plugin > Issue Type: Wish >Reporter: Cesar Izurieta >Assignee: Stephane Nicoll > Fix For: 2.3.2 > > Attachments: maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_2.txt, > maven-ear-plugin_datasource-patch_final.txt > > > It would be nice to be able to add a jarModule as: > > > mysql-ds.xml > true > > > So the resulting application.xml looks like: > > ... > > mysql-ds.xml > > > This would help to deploy jboss datasources with the ear. -- 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-3165) Publish the reference docs for 2.0.7
Publish the reference docs for 2.0.7 Key: MNG-3165 URL: http://jira.codehaus.org/browse/MNG-3165 Project: Maven 2 Issue Type: Task Components: Documentation: General Affects Versions: 2.0.7 Reporter: Wendy Smoak The reference documentation for Maven 2.0.7 is missing from the website. See: http://maven.apache.org/ref/ This needs to be part of the release process. -- 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-273) Regression: NullPointerException at end of standalone "release:perform"
[
http://jira.codehaus.org/browse/MRELEASE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105665
]
Curt Arnold commented on MRELEASE-273:
--
This is also occuring with the log4j releases. I'm able to muddle through by
specifying -Dgoals="test site-deploy assembly:attached deploy" to push the NPE
way back until all the essential actions have been accomplished, but it is a
real pain. If you set up your machine to redirect people.apache.org to
localhost (or some other machine under your control), set up
/www/people.apache.org/builds/logging/repo on localhost to act as the staging
repo, and add a server section to your conf/settings.xml like:
logging.repo
USERNAME for people.apache.org
/home/ubuntu/.ssh/id_rsa
Then you should be able to recreate the NPE by:
mvn release:perform
-DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/logging/log4j/tags/v1_2_15_rc6
If that doesn't work, try adding a -Dgoals="deploy"
> Regression: NullPointerException at end of standalone "release:perform"
> ---
>
> Key: MRELEASE-273
> URL: http://jira.codehaus.org/browse/MRELEASE-273
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
> Environment: Maven 2.0.7, maven-release-plugin 2.0-alpha-6
>Reporter: Max Bowsher
>Priority: Blocker
>
> I executed "mvn release:perform -DconnectionUrl=scm:svn:..". The actual
> performing succeeded, but then the plugin failed with a NullPointerException
> - it seems that the plugin attempts to unconditionally run code analogous to
> "mvn release:clean", but this is inappropriate because release:perform is not
> supposed to require a project to be able to run.
> Output:
> {noformat}
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> [INFO] Total time: 28 seconds
> [INFO] Finished at: Thu Aug 02 12:53:49 BST 2007
> [INFO] Final Memory: 13M/23M
> [INFO]
>
> [INFO] Cleaning up after release...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getReleasePom(ReleaseUtil.java:73)
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getStandardPom(ReleaseUtil.java:61)
> at
> org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.getPomBackup(AbstractBackupPomsPhase.java:37)
> at
> org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.deletePomBackup(AbstractBackupPomsPhase.java:51)
> at
> org.apache.maven.shared.release.phase.CreateBackupPomsPhase.clean(CreateBackupPomsPhase.java:70)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.clean(DefaultReleaseManager.java:427)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:324)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:267)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:260)
> at
> org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:102)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.Na
