[jira] Commented: (MRELEASE-215) mvn release:perform deploys an incomplete pom into repository.
[ http://jira.codehaus.org/browse/MRELEASE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93589 ] Emmanuel Venisse commented on MRELEASE-215: --- can you try with 2.0-beta-5-SNAPSHOT? I think it will work because this version doesn't modify a lot POMs but only the content of tags in xml > mvn release:perform deploys an incomplete pom into repository. > -- > > Key: MRELEASE-215 > URL: http://jira.codehaus.org/browse/MRELEASE-215 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Environment: Windows XP, Java 1.05 >Reporter: Marco Antonio Villalobos, Jr. >Priority: Blocker > Attachments: kineteque-jsf-1.0.5.pom, pom.xml > > > I have had this problem in Maven 2.04, and Maven 2.0.6. My manager also had > this problem independently. > When using the mvn release:perform plugin, the pom that it posts into the > repository is cut off somewhere in the middle, creating invalid xml, and > furthermore, an invalid pom. > Then, when another project that uses this dependency attempts to use this > dependency, > it cannot be resolved because the xml in the repository is wrong. > I want to maven through a complete cycle > test compile release. > Attached is the project pom, and and the generated pom version 1.0.5 > I would actually private project source if there is a guarantee that it would > be kept private and my property. > I consider this a stopper because I want to release my code, but now I cannot > because of this bug unless I choose NOT to use Maven. But I love Maven, and > I want to continue using it. -- 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-217) BUILD FAILURE: The version could not be updated: ${version}
[
http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93590
]
Emmanuel Venisse commented on MRELEASE-217:
---
a workaround would be to use ${project.version} instead of ${version}
> BUILD FAILURE: The version could not be updated: ${version}
> ---
>
> Key: MRELEASE-217
> URL: http://jira.codehaus.org/browse/MRELEASE-217
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: XP Pro SP2
>Reporter: David Hoffer
>Priority: Critical
> Attachments: buildlog.txt, poms-for-release-plugin.zip
>
>
> I manually built 2.0-beta-5 from maven-release-1 tag because of bug in
> 2.0-beta-4. I have found a problem using 2.0-beta-5 with a large
> multi-module project which makes heavy use of ${version} macros. This macro
> is used for the version for any dependency on modules within each module.
> For example in one module where I have a dependency on 3 other modules I have
> this:
>
>
> com.xrite
> xdsiii-driver-api
> ${version}
>
>
> com.xrite
> xdsiii-driver
> ${version}
>
>
> com.xrite
> xdsiii-instrument-dtp22
> ${version}
>
> When I run the prepare phase I get the following error:
> [INFO] Transforming 'X-Rite XDSIII Instrument Drivers'...
> [INFO] Transforming 'X-Rite XDSIII Base Instrument'...
> [INFO] Transforming 'X-Rite XDSIII DTP22 Instrument'...
> [INFO] Updating xdsiii-instrument-base to 1.84
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The version could not be updated: ${version}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: The version could not be updated:
> ${version}
> It starts updating the poms with the new release version and then fails part
> way through the process.
> I will attach some files:
--
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-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93593 ] Damien Lecan commented on MRELEASE-3: - Snapshot of the plugin from rev 530675 doesn't need to have artifacts in the local repository. Good job > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRELEASE-3. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 2.0-beta-5 > release:prepare should not require multimodule artifacts to be in the local > repository > -- > > Key: MRELEASE-3 > URL: http://jira.codehaus.org/browse/MRELEASE-3 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: John Casey >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > > Currently, if you try to run release:prepare on a multimodule project after > removing any of that build's artifacts from the local repository, it will > fail. Investigate why release:prepare needs the multimodule artifacts > installed in the local repository before it can succeed. > To reproduce, comment the following line in it2002/test.sh: > mvn clean install > NOTE: This may have to do with the version resolution code, which is used to > resolve SNAPSHOT versions. -- 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-188) release:perform is not updating some modules to the next version identifier correctly.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93594 ] Emmanuel Venisse commented on MRELEASE-188: --- I don't consider an artifactId written on multiple lines is correct. But if you consider it's correct too, I'll let you fix it ;) > release:perform is not updating some modules to the next version identifier > correctly. > -- > > Key: MRELEASE-188 > URL: http://jira.codehaus.org/browse/MRELEASE-188 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: Barrie Treloar >Assignee: Barrie Treloar > > For some reason the release:prepare is not correctly removing -SNAPSHOT from > some module files, most of them have been correctly transformed only one has > not been. > I am manually double checking whether the tagged version of the file has been > modified correctly prior to running release:perform. > I hope to put together a test case for this problem. I'm not sure why it is > occurring and without a test case it will be impossible for someone else to > resolve. > Work around: > If there is an error, copy the pom.xml to a safe place. > From the CVS History get the contents of the tagged version for release and > then make the necessary modifications and commit them. The file then needs to > be retagged to use the release tag. > Now copy back the contents of the saved pom.xml, which contains the version > id's updated to the next snapshot identifiers. Make sure to fix the same > versions that had problems as above to the correct new snapshot value. -- 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-319) Web UI Tests for Archiva Search Function
Web UI Tests for Archiva Search Function Key: MRM-319 URL: http://jira.codehaus.org/browse/MRM-319 Project: Archiva Issue Type: Test Components: web application Reporter: Henry S. Isidro -- 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: (MRM-319) Web UI Tests for Archiva Search Function
[ http://jira.codehaus.org/browse/MRM-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry S. Isidro updated MRM-319: Attachment: MRM-319-archiva-webapp-test.patch FIle Attached: MRM-319-archiva-webapp-test.patch > Web UI Tests for Archiva Search Function > > > Key: MRM-319 > URL: http://jira.codehaus.org/browse/MRM-319 > Project: Archiva > Issue Type: Test > Components: web application >Reporter: Henry S. Isidro > Attachments: MRM-319-archiva-webapp-test.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] Closed: (MEV-517) incomplete maven-scm-plugin 1.0-rc1
[ http://jira.codehaus.org/browse/MEV-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MEV-517. Assignee: Emmanuel Venisse Resolution: Fixed > incomplete maven-scm-plugin 1.0-rc1 > --- > > Key: MEV-517 > URL: http://jira.codehaus.org/browse/MEV-517 > Project: Maven Evangelism > Issue Type: Bug > Components: Missing POM >Reporter: Tomasz Pik >Assignee: Emmanuel Venisse > > there's only jar file for maven-scm-plugin 1.0-rc1, there's no pom file and > maven-metadata do not list 1.0-rc1. > it looks that sync from > http://people.apache.org/~evenisse/stage/repo/org/apache/maven/plugins/maven-scm-plugin/ > is incomplete -- 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-320) ProxiedDavServer breaks update policy
ProxiedDavServer breaks update policy - Key: MRM-320 URL: http://jira.codehaus.org/browse/MRM-320 Project: Archiva Issue Type: Bug Components: WebDAV interface Affects Versions: 1.0 Reporter: nicolas de loof Priority: Minor The ProxiedDavServer use hasResource() to bypass proxyRequestHandler if requested resource is allready in the managed repo. This sounds a good optimization, but breaks any update capability of archiva. When I deploy a new snapshot, developper never get an updated one... -- 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: (MPJETTY-11) java.lang.ClassCastException while executing mvn jetty:run
java.lang.ClassCastException while executing mvn jetty:run -- Key: MPJETTY-11 URL: http://jira.codehaus.org/browse/MPJETTY-11 Project: maven-jetty-plugin Issue Type: Bug Environment: uname -srvmpio Linux 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 unknown unknown GNU/Linux java -version java version "1.6.0" Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0-b105, mixed mode) Reporter: MartinFunk Attachments: pom.xml java.lang.ClassCastException while executing mvn jetty:run when jetty dependency is present. Been creating a webapp project using: mvn archetype:create -DgroupId=foo.bar -DartifactId=foo-bar -DarchetypeArtifactId=maven-archetype-webapp Adding the jetty-plugin as described in: http://www.mortbay.org/maven-plugin/howto.html works fine. Using mvn jetty:run starts the server, the application can be seen with a browser. After adding ... org.mortbay.jetty jetty 6.1.1 to the pom.xml, mvn jetty:run crashes with a ClassCastException. Attached is the pom.xml I used. Martin -- 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-217) BUILD FAILURE: The version could not be updated: ${version}
[
http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93657
]
David Hoffer commented on MRELEASE-217:
---
I tried that and it skips it, here is the log:
23:20:16]: Ignoring artifact version update for expression: ${project.version}
Now maybe I didn't understand what this means. I thought it was not
understanding what to do so it was skipped. Are you saying that keeping
${project.version} in the version tag is what maven prefers and it will know
what this means (always replace with this artifacts version)?
Or is it better to use ${version} and have it replaced with the actual version
in the POM? Which is the more correct behavior?
-dh
> BUILD FAILURE: The version could not be updated: ${version}
> ---
>
> Key: MRELEASE-217
> URL: http://jira.codehaus.org/browse/MRELEASE-217
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: XP Pro SP2
>Reporter: David Hoffer
>Priority: Critical
> Attachments: buildlog.txt, poms-for-release-plugin.zip
>
>
> I manually built 2.0-beta-5 from maven-release-1 tag because of bug in
> 2.0-beta-4. I have found a problem using 2.0-beta-5 with a large
> multi-module project which makes heavy use of ${version} macros. This macro
> is used for the version for any dependency on modules within each module.
> For example in one module where I have a dependency on 3 other modules I have
> this:
>
>
> com.xrite
> xdsiii-driver-api
> ${version}
>
>
> com.xrite
> xdsiii-driver
> ${version}
>
>
> com.xrite
> xdsiii-instrument-dtp22
> ${version}
>
> When I run the prepare phase I get the following error:
> [INFO] Transforming 'X-Rite XDSIII Instrument Drivers'...
> [INFO] Transforming 'X-Rite XDSIII Base Instrument'...
> [INFO] Transforming 'X-Rite XDSIII DTP22 Instrument'...
> [INFO] Updating xdsiii-instrument-base to 1.84
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The version could not be updated: ${version}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: The version could not be updated:
> ${version}
> It starts updating the poms with the new release version and then fails part
> way through the process.
> I will attach some files:
--
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-188) release:perform is not updating some modules to the next version identifier correctly.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93668 ] Barrie Treloar commented on MRELEASE-188: - Fair enough. I vaguely remember something about text data of XML tags to allow whitespace before and after the text. It should at the least fail with an error, but I don't remember it doing so, it just failed to transform the file correctly. > release:perform is not updating some modules to the next version identifier > correctly. > -- > > Key: MRELEASE-188 > URL: http://jira.codehaus.org/browse/MRELEASE-188 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: Barrie Treloar >Assignee: Barrie Treloar > > For some reason the release:prepare is not correctly removing -SNAPSHOT from > some module files, most of them have been correctly transformed only one has > not been. > I am manually double checking whether the tagged version of the file has been > modified correctly prior to running release:perform. > I hope to put together a test case for this problem. I'm not sure why it is > occurring and without a test case it will be impossible for someone else to > resolve. > Work around: > If there is an error, copy the pom.xml to a safe place. > From the CVS History get the contents of the tagged version for release and > then make the necessary modifications and commit them. The file then needs to > be retagged to use the release tag. > Now copy back the contents of the saved pom.xml, which contains the version > id's updated to the next snapshot identifiers. Make sure to fix the same > versions that had problems as above to the correct new snapshot value. -- 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-217) BUILD FAILURE: The version could not be updated: ${version}
[
http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93661
]
Emmanuel Venisse commented on MRELEASE-217:
---
the plugin skip it because ${project.version} is the version of the current POM
and this version is resolved/modified elsewhere by the plugin (when the user
choose the module version). ${project.version} is kept in the tag and have the
same effect to replace it by the real version because maven interpolate it.
> BUILD FAILURE: The version could not be updated: ${version}
> ---
>
> Key: MRELEASE-217
> URL: http://jira.codehaus.org/browse/MRELEASE-217
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: XP Pro SP2
>Reporter: David Hoffer
>Priority: Critical
> Attachments: buildlog.txt, poms-for-release-plugin.zip
>
>
> I manually built 2.0-beta-5 from maven-release-1 tag because of bug in
> 2.0-beta-4. I have found a problem using 2.0-beta-5 with a large
> multi-module project which makes heavy use of ${version} macros. This macro
> is used for the version for any dependency on modules within each module.
> For example in one module where I have a dependency on 3 other modules I have
> this:
>
>
> com.xrite
> xdsiii-driver-api
> ${version}
>
>
> com.xrite
> xdsiii-driver
> ${version}
>
>
> com.xrite
> xdsiii-instrument-dtp22
> ${version}
>
> When I run the prepare phase I get the following error:
> [INFO] Transforming 'X-Rite XDSIII Instrument Drivers'...
> [INFO] Transforming 'X-Rite XDSIII Base Instrument'...
> [INFO] Transforming 'X-Rite XDSIII DTP22 Instrument'...
> [INFO] Updating xdsiii-instrument-base to 1.84
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] The version could not be updated: ${version}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: The version could not be updated:
> ${version}
> It starts updating the poms with the new release version and then fails part
> way through the process.
> I will attach some files:
--
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] Work stopped: (MRM-318) Web UI test for Archiva webapp 'Proxied Repositories'
[ http://jira.codehaus.org/browse/MRM-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-318 stopped by Maria Odea Ching. > Web UI test for Archiva webapp 'Proxied Repositories' > - > > Key: MRM-318 > URL: http://jira.codehaus.org/browse/MRM-318 > Project: Archiva > Issue Type: Task > Components: web application >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > -- 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-318) Web UI test for Archiva webapp 'Proxied Repositories'
[ http://jira.codehaus.org/browse/MRM-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-318. Resolution: Fixed Fixed in r530375 > Web UI test for Archiva webapp 'Proxied Repositories' > - > > Key: MRM-318 > URL: http://jira.codehaus.org/browse/MRM-318 > Project: Archiva > Issue Type: Task > Components: web application >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > -- 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-1491) Upload SNMP4J Agent 1.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felipe Leme updated MAVENUPLOAD-1491: - Summary: Upload SNMP4J Agent 1.1.1 (was: Upload SNMP4J 1.1.1) > Upload SNMP4J Agent 1.1.1 > - > > Key: MAVENUPLOAD-1491 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1491 > Project: maven-upload-requests > Issue Type: Task >Reporter: Felipe Leme > > I based the pom on snmp4j that is on Ibiblio > http://mirrors.ibiblio.org/pub/mirrors/maven2/org/snmp4j/snmp4j/1.7.1/ > Also, I got the jars from: > http://www.snmp4j.org/html/download.html > Finally, it depends on snmp4j-1.8.1, which was requested at MAVENUPLOAD-1490 > -- Felipe -- 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-1491) Upload SNMP4J 1.1.1
Upload SNMP4J 1.1.1 --- Key: MAVENUPLOAD-1491 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1491 Project: maven-upload-requests Issue Type: Task Reporter: Felipe Leme I based the pom on snmp4j that is on Ibiblio http://mirrors.ibiblio.org/pub/mirrors/maven2/org/snmp4j/snmp4j/1.7.1/ Also, I got the jars from: http://www.snmp4j.org/html/download.html Finally, it depends on snmp4j-1.8.1, which was requested at MAVENUPLOAD-1490 -- Felipe -- 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-218) Check if properties contains SNAPSHOT
Check if properties contains SNAPSHOT - Key: MRELEASE-218 URL: http://jira.codehaus.org/browse/MRELEASE-218 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Emmanuel Venisse Fix For: 2.0-beta-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-218) Check if properties contains SNAPSHOT
[ http://jira.codehaus.org/browse/MRELEASE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated MRELEASE-218: -- Description: Actually, if a property contains a SNAPSHOT verion but it isn't used in dependencies definitions because it's used elsewhere (for example, resources filtering), the pom is released with this SNAPSHOT value Fix Version/s: 2.0-beta-5 > Check if properties contains SNAPSHOT > - > > Key: MRELEASE-218 > URL: http://jira.codehaus.org/browse/MRELEASE-218 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: Emmanuel Venisse > Fix For: 2.0-beta-5 > > > Actually, if a property contains a SNAPSHOT verion but it isn't used in > dependencies definitions because it's used elsewhere (for example, resources > filtering), the pom is released with this SNAPSHOT value -- 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: (MASSEMBLY-202) Silent failure: declared with multiple includes
Silent failure: declared with multiple includes
---
Key: MASSEMBLY-202
URL: http://jira.codehaus.org/browse/MASSEMBLY-202
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
Reporter: Graham Leggett
When attempting to add a dependency to an assembly _without_ unpacking the
dependency using the following snippet of assembly, the dependecies are
silently ignored:
alchemy:alchemy-quant:jar:${os-platform}
alchemy:alchemy-quant:ctf:${os-platform}
false
runtime
It turns out the above config makes no sense - multiple dependencies match the
includes rule, and yet an outputFileNameMapping has been defined, which only
makes sense when it matches a single include line.
In this case a proper error message needs to be thrown to explain that when
outputFileNameMapping is present, only one include can be present. Currently
assembly succeeds silently while doing nothing, causing much confusion.
--
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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
artifact:deploy - The name of deploying element in snapshot repository is wrong --- Key: MANTTASKS-67 URL: http://jira.codehaus.org/browse/MANTTASKS-67 Project: Maven 2.x Ant Tasks Issue Type: Bug Affects Versions: 2.0.6 Reporter: David N'DIAYE Attachments: testSnapshots.zip The zip file contains test with Ant. To launch it : ant test. I try to deploy a snapshot artifact in repository So, my pom.xml contains a version with the extension '-SNAPSHOT' And in my build file Ant i do this : In the repository the name of the artifact is --SNAPSHOT. instead of --.-- Another problem, i try to upload 2 attachments with my artifact (javadoc and java-source), and the buildNumber in the meta-data.xml increment by 3 instead of 1 You can test it with : ant testWithAttach -- 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: (MASSEMBLY-203) assembly:attached creates empty assemblies in reactor builds, but works fine in normal builds
assembly:attached creates empty assemblies in reactor builds, but works fine in normal builds - Key: MASSEMBLY-203 URL: http://jira.codehaus.org/browse/MASSEMBLY-203 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Environment: java version "1.5.0_09" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode) Reporter: Graham Leggett When attaching an assemply to the package phase as below, and running mvn install, the assembly is built without a problem. If however the assembly is a sub-artifact built as part of a reactor / multimodule build, mvn install in the root pom produces an empty assembly. The kludge workaround is to cd to the assembly artifact directory and run mvn install from there. maven-assembly-plugin 2.2-beta-1 assembly.xml make-assembly package attached -- 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: (SCM-300) CVS doesn't close it's session after checkout
CVS doesn't close it's session after checkout - Key: SCM-300 URL: http://jira.codehaus.org/browse/SCM-300 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-cvs Affects Versions: future Environment: Linux, Sun JDK 1.4. Continuum built from trunk. Reporter: Hilco Wijbenga We've been trying to set up Continuum and consequently we started running some builds. It all worked nicely until the CVS server ran out of inodes in its /tmp directory. It looks like it's not the normal checkouts that people do that's causing this ... it appears to be Continuum. We tried a small build with Continuum and lo and behold: /tmp had a new directory that was not deleted at the end of the checkout. So we're fairly certain it's something Continuum related. CVS creates a sort of cache directory (in /tmp) for each checkout (it stores the CVS directories, not any of the files that are being checked out) and this directory (and all of its *many* subdirectories) are not being deleted. Apparently, it doesn't notice that the checkout has finished. Something like a session not being closed. After three days of this our server runs out of inodes and nothing works anymore. We've created a cron job to remove these CVS directories from /tmp at the end of the day so we have a workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-319) true cannot be overridden using mvn -Dmaven.test.skip=false test
true cannot be overridden using mvn -Dmaven.test.skip=false test - Key: SUREFIRE-319 URL: http://jira.codehaus.org/browse/SUREFIRE-319 Project: Maven Surefire Issue Type: Bug Environment: java version "1.5.0_09" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode) Reporter: Graham Leggett If the pom file is configured to skip tests using true, and an attempt is made to override this on the command line using mvn -Dmaven.test.skip=false test, the attempt does not work (the test is still skipped). In theory, the command line flag should override the pom setting. -- 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-2377) maven-metadata not re-read after failure
[
http://jira.codehaus.org/browse/MNG-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2377:
---
Fix Version/s: 2.1-alpha-1
> maven-metadata not re-read after failure
>
>
> Key: MNG-2377
> URL: http://jira.codehaus.org/browse/MNG-2377
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0-alpha-1
>Reporter: Kenney Westerhof
>Assignee: Jason van Zyl
>Priority: Minor
> Fix For: 2.1-alpha-1
>
>
> A bug in deploy (not setting filePermissions correctly on deploy) caused the
> maven-metadata...xml and the artifacts/poms
> to be unreadable.
> When building a project with a dep on a SNAPSHOT artifact on the faulty
> remote repository, the maven-metadata can not be read.
> Maven creates a maven-metadata...xml with the following content (sample):
> {noformat}
>
> com.neonics.container
> bundle-factory-maven
> 1.0-SNAPSHOT
>
> {noformat}
> After fixing the permissions I restart the build, but the metadata file is
> not re-read, resulting in Maven thinking
> 1.0-SNAPSHOT is the actual version and trying to get
> ...artifact/1.0-SNAPSHOT/artifact-1.0-SNAPSHOT.pom
> which does not exist.
> Touching the files on the remote repo doesn't help either.
> Only when running with -U the metadata file is retrieved (another solution is
> to purge files from
> the local repository).
> I think Maven should not create the metadata file if it can't be retrieved
> AND if the non-timestamped
> SNAPSHOT version doesn't exist.
> I can see why the placeholder metadata files reduces future requests for this
> file,
> but that's only useful if there _are_ future requests. There are indeed
> repeated requests for the pom
> and artifact, even though they also don't exist. I think that only when the
> artifact 1.0-SNAPSHOT exists
> and the metadata file doesn't, it's safe to put a placeholder metadata file
> in the local 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] Updated: (MCHECKSTYLE-59) Checkstyle Report fails if propertyExpansion contains file names
[
http://jira.codehaus.org/browse/MCHECKSTYLE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Behnke updated MCHECKSTYLE-59:
---
Attachment: MCHECKSTYLE-59-PATCH.patch
Please find the attached patch. It resolves the issue Carsten pointed out by
quoting all backslash characters of the propertyExpansion value. Hence,
expressions like dir=${basedir} will
work on Windows systems. However, there is also a trade-off: You won't be able
to pass unicode characters such as \u20ac anymore (which is a minor problem
IMO).
> Checkstyle Report fails if propertyExpansion contains file names
>
>
> Key: MCHECKSTYLE-59
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-59
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Windows XP, JDK 1.4, Maven 2.0.4
>Reporter: Carsten Karkola
>Assignee: Joakim Erdfelt
> Attachments: MCHECKSTYLE-59-PATCH.patch
>
>
> The chechkstyle plugin fails on windows plattforms, if the propertyExpansion
> element contains file names like
>
> mms.suppressions.file=${basedir}/../../project/resources/checkstyle/suppressions.xml
> The backslashes in ${basedir} (like D:\foo\bar) are missing (D:foobar) and
> checkstyle fails. It seems to be an issue with StringInputStream.
> I've replaced the following old code in CheckstyleReport.java
> if ( StringUtils.isNotEmpty( propertyExpansion ) )
> {
> p.load( new StringInputStream( propertyExpansion ) );
> }
> with the new Code
> if ( StringUtils.isNotEmpty( propertyExpansion ) ) {
> BufferedReader reader = new BufferedReader(new
> StringReader(propertyExpansion));
> String line = reader.readLine();
> while (line != null) {
> int delimPosition = line.indexOf('=');
> if (delimPosition > -1) {
> String name = line.substring(0, delimPosition).trim();
> delimPosition++;
> if (delimPosition < line.length()) {
> String value = line.substring(delimPosition).trim();
> if (value.length() > 0) {
> p.put(name, value);
> getLog().info("Property: " + name + " = " +
> p.getProperty(name));
> }
> }
> }
> line = reader.readLine();
> }
> reader.close();
> }
> and it works.
> Regards, carsten
--
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-516) Fix file name of xml-apis 1.3.04 sources attachment
[ http://jira.codehaus.org/browse/MEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-516. -- Assignee: Carlos Sanchez Resolution: Fixed > Fix file name of xml-apis 1.3.04 sources attachment > --- > > Key: MEV-516 > URL: http://jira.codehaus.org/browse/MEV-516 > Project: Maven Evangelism > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > The sources file has the wrong file name. > It is: > xml-apis-1.3.04-source.jar > It should be: > xml-apis-1.3.04-sources.jar -- 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-1475) Upload EasyMock class extension 2.2.2 to maven 1 and 2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1475. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload EasyMock class extension 2.2.2 to maven 1 and 2 repo > --- > > Key: MAVENUPLOAD-1475 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1475 > Project: maven-upload-requests > Issue Type: Task >Reporter: Henri Tremblay >Assignee: Carlos Sanchez > > Can you please upload EasyMock class extension 2.2.2 to maven 1 and 2 > 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: (MAVENUPLOAD-1478) Upload fastutil:fastutil:jar:5.0.9 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1478. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload fastutil:fastutil:jar:5.0.9 to ibiblio > - > > Key: MAVENUPLOAD-1478 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1478 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/fastutil-5.0.9-bundle.jar > http://fastutil.dsi.unimi.it/ > fastutil extends the Java Collections Framework by providing type-specific > maps, sets, lists and queues with a small memory footprint and fast access > and insertion; it also includes a fast I/O API for binary and text files. -- 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-1477) Upload c3p0:c3p0:jar:0.9.1.1 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1477. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload c3p0:c3p0:jar:0.9.1.1 to ibiblio > --- > > Key: MAVENUPLOAD-1477 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1477 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/c3p0-0.9.1.1-bundle.jar > http://c3p0.sourceforge.net/ > c3p0 is an easy-to-use library for augmenting traditional > (DriverManager-based) JDBC drivers with JNDI-bindable DataSources, including > DataSources that implement Connection and Statement Pooling, as described by > the jdbc3 spec and jdbc2 std extension. -- 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-1480) Upload org.openspml:openspml:jar:0.5 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1480. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload org.openspml:openspml:jar:0.5 to ibiblio > --- > > Key: MAVENUPLOAD-1480 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1480 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/openspml-0.5-bundle.jar > http://www.openspml.org/ > An open source client code that supports the Service Provisioning Markup > Language (SPML) developed by the OASIS Provisioning Services Technical > Committee (PSTC). -- 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-1479) Upload org.hibernate:hibernate:jar:3.2.3.ga to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1479. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload org.hibernate:hibernate:jar:3.2.3.ga to ibiblio > -- > > Key: MAVENUPLOAD-1479 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1479 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/hibernate-3.2.3.ga-bundle.jar > http://www.hibernate.org/ > Relational Persistence for 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-1481) Upload com.novell.ldap:jldap:jar:4.3 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1481. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload com.novell.ldap:jldap:jar:4.3 to ibiblio > --- > > Key: MAVENUPLOAD-1481 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1481 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/jldap-4.3-bundle.jar > http://www.openldap.org/jldap/ > The LDAP Class Libraries for Java (JLDAP) enable you to write applications to > access, manage, update, and search for information stored in directories > accessible using LDAPv3. -- 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-1483) Please synchronize the jDTAUS repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1483. --- Assignee: Carlos Sanchez Resolution: Fixed > Please synchronize the jDTAUS repository > > > Key: MAVENUPLOAD-1483 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1483 > Project: maven-upload-requests > Issue Type: Task >Reporter: Christian Schulte >Assignee: Carlos Sanchez > Attachments: org.jdtaus.sh > > -- 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-1482) Upload javadoc attachment for xmlbeans:xbean:jar:2.2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1482. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload javadoc attachment for xmlbeans:xbean:jar:2.2.0 > -- > > Key: MAVENUPLOAD-1482 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1482 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/xbean-2.2.0-javadoc.jar > http://xmlbeans.apache.org/ > Note that this is just the javadocs. The main artifact is already on > ibiblio, but it is missing javadoc. -- 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-1484) Please upload EZMorph-1.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93712 ] Carlos Sanchez commented on MAVENUPLOAD-1484: - findbugs-maven-plugin is a snapshot, you can't release with snapshot dependencies. You need to remove the codehaus sanpshot repository > Please upload EZMorph-1.0.2 > --- > > Key: MAVENUPLOAD-1484 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1484 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > EZMorph is simple java library for transforming an Object to another Object. > This release covers minor bugfixes. -- 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-1485) Upload EasyMock-PropertyUtils-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1485. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload EasyMock-PropertyUtils-1.1 > - > > Key: MAVENUPLOAD-1485 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1485 > Project: maven-upload-requests > Issue Type: Task >Reporter: Stephen Duncan Jr >Assignee: Carlos Sanchez > > Code hosted site: > http://code.google.com/p/jrduncans/ -- 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-1486) Please add Beanshell 1.3.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1486. --- Assignee: Carlos Sanchez Resolution: Fixed > Please add Beanshell 1.3.0 > -- > > Key: MAVENUPLOAD-1486 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1486 > Project: maven-upload-requests > Issue Type: Task >Reporter: Steve Loughran >Assignee: Carlos Sanchez > > This is bsh 1.3.0 from beanshell.org with a POM file to go with. > 1. there is already the bsh 2.0.4 resource in the repository; this goes into > the same hierarchy. > 2. the license only declares the LGPL license, even though Sun's Public > License is also listed on the beanshell site as the alternate license. Sun > have dropped the SPL; even its URLs are no longer there. -- 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-1487) Please upload OpenXRI Syntax bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1487. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload OpenXRI Syntax bundle > --- > > Key: MAVENUPLOAD-1487 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1487 > Project: maven-upload-requests > Issue Type: Task >Reporter: William Tan >Assignee: Carlos Sanchez > > http://www.openxri.org/maven/org.openxri.syntax/openxri-syntax-1.0.1-bundle.jar > http://www.openxri.org/ > http://sourceforge.net/project/memberlist.php?group_id=132761 > OpenXRI is an open source project reference implementation of the XRI > (Extensible Resource Identifier) abstract identifier resolution protocol > based on the specifications from the OASIS XRI Technical Committee. -- 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-1488) rxtx. upload : java serial and parallel I/O API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93713 ] Carlos Sanchez commented on MAVENUPLOAD-1488: - groupId is incorrect should be org.rxtx and artifactId rxtx > rxtx. upload : java serial and parallel I/O API > --- > > Key: MAVENUPLOAD-1488 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1488 > Project: maven-upload-requests > Issue Type: Task >Reporter: Julien Vermillard > > RXTX is a native lib providing serial and parallel communication for the Java > Development Toolkit (JDK). All deliverables are under the gnu LGPL license. > I upload it because I need it for apache MINA (for more info : [EMAIL > PROTECTED]), I'm not an RXTX developer. -- 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-1489) com.jgoodies-binding-1.4.0 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1489. --- Assignee: Carlos Sanchez Resolution: Fixed > com.jgoodies-binding-1.4.0 upload request > - > > Key: MAVENUPLOAD-1489 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1489 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Stefan Prange >Assignee: Carlos Sanchez > > I'm sending this request on behalf of Karsten Lentzsch, the author of this > library. > He asked for help on uploading this maven bundle on the mailing list [EMAIL > PROTECTED] on April 18, 2007 (see > https://binding.dev.java.net/servlets/SummarizeList?listName=users) -- 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-1462) Request to upload hamcrest library 1.0 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93714 ] Carlos Sanchez commented on MAVENUPLOAD-1462: - proof? your name doesn't show up in whois http://www.pir.org/whois > Request to upload hamcrest library 1.0 bundle > - > > Key: MAVENUPLOAD-1462 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1462 > Project: maven-upload-requests > Issue Type: Task >Reporter: Joe Walnes > -- 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-1491) Upload SNMP4J Agent 1.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1491. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload SNMP4J Agent 1.1.1 > - > > Key: MAVENUPLOAD-1491 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1491 > Project: maven-upload-requests > Issue Type: Task >Reporter: Felipe Leme >Assignee: Carlos Sanchez > > I based the pom on snmp4j that is on Ibiblio > http://mirrors.ibiblio.org/pub/mirrors/maven2/org/snmp4j/snmp4j/1.7.1/ > Also, I got the jars from: > http://www.snmp4j.org/html/download.html > Finally, it depends on snmp4j-1.8.1, which was requested at MAVENUPLOAD-1490 > -- Felipe -- 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-1490) Upload SNMP4J 1.8.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1490. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload SNMP4J 1.8.1 > --- > > Key: MAVENUPLOAD-1490 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1490 > Project: maven-upload-requests > Issue Type: Task >Reporter: Felipe Leme >Assignee: Carlos Sanchez > > I based the pom on the current version uploaded at ibiblio (1.7.1): > http://mirrors.ibiblio.org/pub/mirrors/maven2/org/snmp4j/snmp4j/1.7.1/ > Also, I got the jars from: > http://www.snmp4j.org/html/download.html > -- Felipe -- 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-1484) Please upload EZMorph-1.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93717 ] Andres Almiray commented on MAVENUPLOAD-1484: - Right, sorry for the oversight. Will correct the configuration and post when updated. Thanks. > Please upload EZMorph-1.0.2 > --- > > Key: MAVENUPLOAD-1484 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1484 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > EZMorph is simple java library for transforming an Object to another Object. > This release covers minor bugfixes. -- 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: (CONTINUUM-990) Pass some continuum information to build tools when executing a build
[ http://jira.codehaus.org/browse/CONTINUUM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-990: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 moving this to alpha 2 since I just finished alpha 1 releasing...but I'll take this issue and get it applied first thing > Pass some continuum information to build tools when executing a build > - > > Key: CONTINUUM-990 > URL: http://jira.codehaus.org/browse/CONTINUUM-990 > Project: Continuum > Issue Type: New Feature > Components: Core system >Reporter: John Didion >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: maven2-build-properties.diff > > > It would be nice to access some information (specifically build numbers) in > the build script itself - for example, if I wanted to embed the build number > in the jar manifest. > I've attached a patch that does this for m2. I'm not sure if you could > generalize it to work for all builds, or if you'd have to implement it > separately for each build executor. -- 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-2951) profiles.xml doesn't have a public schema url
[ http://jira.codehaus.org/browse/MNG-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint closed MNG-2951. - Resolution: Fixed Fix Version/s: 2.1-alpha-1 done, uploaded the latest trunk version to the site. > profiles.xml doesn't have a public schema url > - > > Key: MNG-2951 > URL: http://jira.codehaus.org/browse/MNG-2951 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.6 >Reporter: Milos Kleint >Assignee: Milos Kleint >Priority: Critical > Fix For: 2.1-alpha-1 > > > the schema for profiles.xml should be put next to the ones for pom.xml and > settings.xml at http://maven.apache.org/xsd -- 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: (MCHANGES-77) Document the variables available to the announcement template.
Document the variables available to the announcement template. -- Key: MCHANGES-77 URL: http://jira.codehaus.org/browse/MCHANGES-77 Project: Maven 2.x Changes Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3 Reporter: Paul Spencer Document the variables available to the announcement template. The list currently includes: releases groupId artifactId version packaging url introduction developmentTeam finalName urlDownload -- 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-1492) Please upload OpenXRI Client bundle
Please upload OpenXRI Client bundle --- Key: MAVENUPLOAD-1492 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1492 Project: maven-upload-requests Issue Type: Task Reporter: William Tan http://www.openxri.org/maven/org.openxri.client/openxri-client-1.0.1-bundle.jar http://www.openxri.org/ http://sourceforge.net/project/memberlist.php?group_id=132761 OpenXRI is an open source project reference implementation of the XRI (Extensible Resource Identifier) abstract identifier resolution protocol based on the specifications from the OASIS XRI Technical Committee. The OpenXRI Client module depends on the syntax module (openxri-syntax) and provides XRI resolution functionality to client applications. -- 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: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test-2.patch This patch contains tweaks to the pom.xml, updating the ant task that copies test resources to the appropriate locations. The AbstractArchivaTestCase is also updated of the resources' names. > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: MRM-317-archiva-webapp-test-2.patch, > MRM-317-archiva-webapp-test.patch, MRM-317-archiva-webapp-test.tar.gz > > -- 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: (MASSEMBLY-200) AssemblyInterpolatorTest.testShouldResolveEnvarHOMEValueInDependencySetOutputDirectory fails on Windows XP
[
http://jira.codehaus.org/browse/MASSEMBLY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MASSEMBLY-200.
Resolution: Fixed
Fix Version/s: 2.2
patch applied.
> AssemblyInterpolatorTest.testShouldResolveEnvarHOMEValueInDependencySetOutputDirectory
> fails on Windows XP
> --
>
> Key: MASSEMBLY-200
> URL: http://jira.codehaus.org/browse/MASSEMBLY-200
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: Windows XP
>Reporter: Barrie Treloar
>Assignee: Barrie Treloar
> Fix For: 2.2
>
> Attachments: MASSEMBLY-200-patch.txt
>
>
> AssemblyInterpolatorTest.testShouldResolveEnvarHOMEValueInDependencySetOutputDirectory
> fails with
> expected:<${env.PATH}> but was:
> This is because AssemblyInterpolatorTest is using
>import org.codehaus.plexus.util.cli.CommandLineUtils;
> instead of
> import org.apache.maven.plugin.assembly.utils.CommandLineUtils;
> and the call to get the envars should be
> Properties envars = CommandLineUtils.getSystemEnvVars( false );
--
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: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: (was: MRM-317-archiva-webapp-test-2.patch) > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > -- 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: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: (was: MRM-317-archiva-webapp-test.tar.gz) > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > -- 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: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: (was: MRM-317-archiva-webapp-test.patch) > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > -- 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: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test-x.patch > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: MRM-317-archiva-webapp-test-x.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] Updated: (MRM-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-317: Attachment: MRM-317-archiva-webapp-test-x.tar.gz > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: MRM-317-archiva-webapp-test-x.patch, > MRM-317-archiva-webapp-test-x.tar.gz > > -- 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-317) Web UI tests for Archiva - Browse
[ http://jira.codehaus.org/browse/MRM-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-317. Resolution: Fixed Patch applied -r530975, thanks :) > Web UI tests for Archiva - Browse > - > > Key: MRM-317 > URL: http://jira.codehaus.org/browse/MRM-317 > Project: Archiva > Issue Type: Test > Components: web application > Environment: Linux FC6, JDK 1.5, Maven 2.0.6 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Maria Odea Ching > Attachments: MRM-317-archiva-webapp-test-x.patch, > MRM-317-archiva-webapp-test-x.tar.gz > > -- 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-319) Web UI Tests for Archiva Search Function
[ http://jira.codehaus.org/browse/MRM-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-319. Resolution: Fixed Patch applied -r530978, thanks! > Web UI Tests for Archiva Search Function > > > Key: MRM-319 > URL: http://jira.codehaus.org/browse/MRM-319 > Project: Archiva > Issue Type: Test > Components: web application >Reporter: Henry S. Isidro >Assignee: Maria Odea Ching > Attachments: MRM-319-archiva-webapp-test.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: (MRM-321) Web UI tests for Archiva - Managed Repositories Configuration
Web UI tests for Archiva - Managed Repositories Configuration - Key: MRM-321 URL: http://jira.codehaus.org/browse/MRM-321 Project: Archiva Issue Type: Test Components: web application Reporter: Napoleon Esmundo C. Ramirez -- 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: (MRM-321) Web UI tests for Archiva - Managed Repositories Configuration
[ http://jira.codehaus.org/browse/MRM-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated MRM-321: Attachment: MRM-321-archiva-webapp-test.patch Attached a patch for testing the configuration of managed repositories. On toggling the Show POM snippet: The POM snippet cannot be verified not to be present using the assertTextNotPresent() method as the POM snippet is always present, just hidden. > Web UI tests for Archiva - Managed Repositories Configuration > - > > Key: MRM-321 > URL: http://jira.codehaus.org/browse/MRM-321 > Project: Archiva > Issue Type: Test > Components: web application >Reporter: Napoleon Esmundo C. Ramirez > Attachments: MRM-321-archiva-webapp-test.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] Closed: (MRM-321) Web UI tests for Archiva - Managed Repositories Configuration
[ http://jira.codehaus.org/browse/MRM-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-321. Resolution: Fixed Patch applied -r530982, thanks! > Web UI tests for Archiva - Managed Repositories Configuration > - > > Key: MRM-321 > URL: http://jira.codehaus.org/browse/MRM-321 > Project: Archiva > Issue Type: Test > Components: web application >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Maria Odea Ching > Attachments: MRM-321-archiva-webapp-test.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-1493) Uploading pyx4me 2.0.1 to The Central Repository
Uploading pyx4me 2.0.1 to The Central Repository Key: MAVENUPLOAD-1493 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy The collection of maven-plugins and Archetype used develop applications for the Java Micro Edition Platform Upload has 3 parent poms to be loaded first. http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- 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
