[jira] Issue Comment Edited: (MAVENUPLOAD-2286) nez sync rule from sourceforge project
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155811#action_155811 ] Christophe Lallement edited comment on MAVENUPLOAD-2286 at 12/1/08 3:11 AM: maybe there is an error and the hostname to sync is: "org.jvyaml","[EMAIL PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","[EMAIL PROTECTED]",, was (Author: christophe): maybe there is an error and the hostname to sync is: "org.jvyaml","[EMAIL PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, > nez sync rule from sourceforge project > -- > > Key: MAVENUPLOAD-2286 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2286 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Christophe Lallement > > "org.jvyaml","[EMAIL > PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, -- 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-3880) package phase devided into more specific phases
package phase devided into more specific phases --- Key: MNG-3880 URL: http://jira.codehaus.org/browse/MNG-3880 Project: Maven 2 Issue Type: Improvement Components: Plugins and Lifecycle Affects Versions: 2.0.9 Reporter: Anders Kr. Andersen Currently the command mvn package will produce a zipped result file like xx.war or xxx.jar So I belive it must always be... I suggest that the phase is devided into multiple pre phases like: package-copy --> copies files to target/xxx-war (the prezipped directory structure) package-manifest --> generates the manifest to be packed into the zipped result package-maven --> generates the maven META-INF/maven files package-compress --> zips the target/xxx-war into the file target/xxx-war.war The reasoning for these suggestions is that I had a situation where I had to add more files into the unpacked result. This ended up more jobbi than I had thought because I had to manage the manifest, maven and compress as well. Best regards /Anders PS: My sample is a Weblogic Integration Problem with task weblogic.ant.taskdefs.build.AnnotationManifestTask The task will go through all classes and jars in the result and make a kind of index and place the index into META-INF. My code got ugly I had to run the task yes, ofcause.. But I had to do much more than I hoped. 1) MANIFEST.MF (maven generates it under the final ZIP process) I had to steal it from mavens ZIP 2) META-INF/maven/ (Maven also generates it under the final ZIP process). I had to steal this as well 3) the package phase will do the compress as well. I had to zip again !!! (Maybe I could just update existing zip?, but i did not choose that) If I had multiple steps in the package phase I could have made this "customer-plugin" easier... Here is the ugly code -- 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-3881) Properties in plugin poms are not resolved.
Properties in plugin poms are not resolved.
---
Key: MNG-3881
URL: http://jira.codehaus.org/browse/MNG-3881
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.1.0-M1
Environment: Mac ox s
Reporter: Derek Clarkson
I'm testing a plugin I have written to run JUnit 4.x tests. The pom for this
plug uses properties to specify the versions of dependencies. ie.
junit
junit
${junit.version}
org.slf4j
slf4j-api
${slf4j.version}
After compiling and installing the plugin into my local repository, I then
attempt to use in in another project. The project compiles correcly, but then
fails when attempting to resolve the dependecies of my plugin. The faiures
appear to be the plugins dependencies which are versioned by properties. HEre's
an example:
6) org.slf4j:slf4j-api:jar:${slf4j.version}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.slf4j -DartifactId=slf4j-api
-Dversion=${slf4j.version} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.slf4j -DartifactId=slf4j-api
-Dversion=${slf4j.version} -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) dhc.maven2:maven-junit4x-plugin:maven-plugin:0.0.3-SNAPSHOT
2) org.slf4j:slf4j-api:jar:${slf4j.version}
I also see stack traces like this:
Caused by: java.io.FileNotFoundException:
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/${maven.reporting.version}/maven-reporting-impl-${maven.reporting.version}.jar
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83)
... 35 more
[DEBUG] Unable to download the artifact from any repository
And
7 required artifacts are missing.
for artifact:
dhc.maven2:maven-junit4x-plugin:maven-plugin:0.0.3-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:482)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:394)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:337)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginArtifacts(DefaultPluginManager.java:436)
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:279)
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:211)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:186)
at
org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:79)
... 20 more
Plaing around with this I found that if I go into the repository and edit the
pom file to specify the dependency version then that dependency resolves.
>From this I'm inclined to think that when resolving dependencies of plugins,
>that the plugin's pom is not being processed to look for properties to be
>inserted.
--
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-3882) Prevent local repository from also being the remote repository
Prevent local repository from also being the remote repository -- Key: MNG-3882 URL: http://jira.codehaus.org/browse/MNG-3882 Project: Maven 2 Issue Type: Bug Components: Settings Affects Versions: 2.1.0-M1, 2.0.10, 3.0-alpha-1 Reporter: Paul Benedict User list shows that the local repository can be specified as a remote repository. I've confirmed this is true. This is obviously a sore misconfiguration. Let's check that the values are never equal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-443) Only include **/*.java in Java source directories
[ http://jira.codehaus.org/browse/MECLIPSE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156002#action_156002 ] Michael Johns commented on MECLIPSE-443: Yes, that's the default behavior of the compiler plugin: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/CompilerMojo.java?view=markup You can override that behavior to include other types of files. I suppose this plugin should follow that same pattern. > Only include **/*.java in Java source directories > - > > Key: MECLIPSE-443 > URL: http://jira.codehaus.org/browse/MECLIPSE-443 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.5.1 >Reporter: Michael Johns >Assignee: Barrie Treloar >Priority: Minor > Fix For: 2.6 > > Attachments: MECLIPSE-443.2.patch, MECLIPSE-443.patch > > > Since Maven only recognizes *.java files in Java source directories > (src/main/java, or src/test/java, for example), it would be nice if the > plugin produced .classpath files configured the same way. Right now, a > developer can inadvertently leave a non-Java resource in one of those > directories, and everything will work fine in Eclipse. But when the time > comes to produce a package, that artifact will be missing since Maven won't > pick it up. -- 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-2293) Please upload jSSLutils 0.5.1
Please upload jSSLutils 0.5.1 - Key: MAVENUPLOAD-2293 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2293 Project: Maven Upload Requests Issue Type: Wish Reporter: Bruno Harbulot Hello, I'm the developer and project owner of jsslutils. Could you please upload this version of the project in the repository? Thank you, Bruno. -- 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-3883) Add the possibility to use libraries in local computer. to copy it to Maven hierarchy folders (repository).
Add the possibility to use libraries in local computer. to copy it to Maven hierarchy folders (repository). --- Key: MNG-3883 URL: http://jira.codehaus.org/browse/MNG-3883 Project: Maven 2 Issue Type: New Feature Components: Dependencies Affects Versions: 2.0.9 Reporter: Anton Priority: Minor Suggest to make possibilities to use old libraries that has already in the system (computer). If somebody already has big gigabytes of the jar - libraries. (for example JDK, JRE and so on) then just use the command to download that libraries to Maven hierarchy folders. You can check the file name and CHECKSUM to understand it is equal or not. this feature I think, will improve time to download all dependencies from internet and econom time of developments and waiting time. Now I am waiting time about 1-2 hours to download-compile big project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3879) Dependency map and documentation
[ http://jira.codehaus.org/browse/MNG-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156012#action_156012 ] Daniel Kulp commented on MNG-3879: -- Changing the POM format is definitely a huge deal and is something that seems to be constantly discussed on the dev list. :-( Adding stuff to the poms currently breaks users of any previous version of Maven, which is not ideal as many corporations and such are adverse to upgrading.There is an opinion of some people that anything deployed in central needs to be completely readable and usable by all versions of maven. I'm wondering if instead of adding another element (and thus changing the pom schema/format), the parser could just be updated to save any comments in the dependency element.All old versions would just ignore it. For the second part, that would be an enhancement of the dependency:tree plugin: http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html > Dependency map and documentation > > > Key: MNG-3879 > URL: http://jira.codehaus.org/browse/MNG-3879 > Project: Maven 2 > Issue Type: New Feature > Components: Dependencies >Affects Versions: 2.0.9 >Reporter: benson margulies > > This JIRA proposes a feature. I'm willing to try to contribute it given a > modicum of encouragement and guidance. > Over at CXF, we get many questions from users who are completely confounded > by the complex dependency graph that results from our many dependencies and > their many dependencies. I think that they would be less confused by far if > maven gave them a tiny bit of help. > The first part of the idea requires an addition to the core POM, which is why > I'm starting with a JIRA here. I propose to add an 'explanation' element to > the dependency element. This would contain a human-readable string explaining > why the dependency is here. > The second part is a goal that I would propose to call 'dependency-map'. This > would produce a formatted map of the dependency tree -- enriched, of course, > by the comments in the first part. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156014#action_156014
]
Benjamin Bentmann commented on MECLIPSE-414:
bq. I'm looking into why it needs a forked lifecycle...
For goals that are primarily run from the CLI, there is not other way to tell
about generated sources/resources. I.e. without forking a build up to
"generates-resources", the plugin would only see the static source/directories
specified in the POM and would miss stuff that gets dynamically generated.
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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: (MDEP-191) Tidy up logging from unpack
Tidy up logging from unpack
---
Key: MDEP-191
URL: http://jira.codehaus.org/browse/MDEP-191
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: unpack
Affects Versions: 2.0
Reporter: Tom Palmer
Assignee: Brian Fox
Priority: Trivial
Attachments: tidy-unpack-logging.patch
The attached patch changes the logging output from unpacking artifacts by
logging on a single line to make it more consistent with other logging messages
(e.g. installing an artifact). It also logs the includes/excludes only when
they are not null. For example the output (taken from the test run of the
plugin) changes from:
{noformat}
[INFO] Unpacking
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/localTestRepo/test-1.0.jar
to
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory
with includes **/test2.txt and excludes:null
[INFO] Unpacking
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/localTestRepo/test-1.0.jar
to
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory
with includes null and excludes:**/*
{noformat}
to:
{noformat}
[INFO] Unpacking
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/localTestRepo/test-1.0.jar
to
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory
with includes **/test2.txt
[INFO] Unpacking
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/localTestRepo/test-1.0.jar
to
/Users/tom/Development/Projects/maven/plugins/maven-dependency-plugin/target/unit-tests/unpack/outputDirectory
with excludes **/*
{noformat}
--
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-3882) Prevent local repository from also being the remote repository
[ http://jira.codehaus.org/browse/MNG-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156061#action_156061 ] Wendy Smoak commented on MNG-3882: -- What values do you want to compare? The local repo is a path, the remote repo is a url. How would Maven be able to detect this? Usually what happens is that a user takes a local repository, copies it to a server and serves it as a remote repo either with a file:// url or by using a web server in front. Less common is dropping a copy of the local repo filesystem into a repository manager -- and this is less of a problem since Archiva at least can repair the metadata. > Prevent local repository from also being the remote repository > -- > > Key: MNG-3882 > URL: http://jira.codehaus.org/browse/MNG-3882 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.0.10, 2.1.0-M1, 3.0-alpha-1 >Reporter: Paul Benedict > > User list shows that the local repository can be specified as a remote > repository. I've confirmed this is true. This is obviously a sore > misconfiguration. Let's check that the values are never equal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156068#action_156068
]
Barrie Treloar commented on MECLIPSE-414:
-
Isn't that only if the CLI plugin isn't part of the normal lifecycle?
In this case m-eclipse-p is bound to the @phase generate-resources and
therefore any other plugin that manipulates the pom should be visible?
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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-3163) Profile activation based on hostname or IP
[ http://jira.codehaus.org/browse/MNG-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156072#action_156072 ] Jessie Crowe commented on MNG-3163: --- The maven guide seems to imply this already works here: http://maven.apache.org/guides/introduction/introduction-to-profiles.html I cannot seem to get it to work. I tried env.COMPUTERNAME on a windows box, but the profile did not activate. > Profile activation based on hostname or IP > -- > > Key: MNG-3163 > URL: http://jira.codehaus.org/browse/MNG-3163 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Reporter: David J. M. Karlsen >Priority: Minor > Fix For: 3.x > > > It would be very nice to be able to activate profiles based on hostname[s] or > IP-address[es]. > Yes, this could be exported from the system as a systemproperty quite easily > on *NIX with -Dhostname=`hostname` but is a little more tricky on other > platforms - so why not include it in maven itself? > It would be even better if it can be expressed with regex'es or the likes. > WDYT? -- 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-3861) Publish specification on POM construction
[ http://jira.codehaus.org/browse/MNG-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156074#action_156074 ] Shane Isbell commented on MNG-3861: --- I'm also updating this to be in line with current builder code. > Publish specification on POM construction > - > > Key: MNG-3861 > URL: http://jira.codehaus.org/browse/MNG-3861 > Project: Maven 2 > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-1 > > -- 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-3163) Profile activation based on hostname or IP
[ http://jira.codehaus.org/browse/MNG-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessie Crowe updated MNG-3163: -- Attachment: exampleproject.zip Here is an example project that demonstrates trying to load a build profile. According to the maven introduction to build profiles, this should work, but it doesn't seem to. > Profile activation based on hostname or IP > -- > > Key: MNG-3163 > URL: http://jira.codehaus.org/browse/MNG-3163 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Reporter: David J. M. Karlsen >Priority: Minor > Fix For: 3.x > > Attachments: exampleproject.zip > > > It would be very nice to be able to activate profiles based on hostname[s] or > IP-address[es]. > Yes, this could be exported from the system as a systemproperty quite easily > on *NIX with -Dhostname=`hostname` but is a little more tricky on other > platforms - so why not include it in maven itself? > It would be even better if it can be expressed with regex'es or the likes. > WDYT? -- 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] Issue Comment Edited: (MNG-3163) Profile activation based on hostname or IP
[ http://jira.codehaus.org/browse/MNG-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156075#action_156075 ] Jessie Crowe edited comment on MNG-3163 at 12/1/08 2:29 PM: Here is an example project that demonstrates trying to load a build profile. According to the maven introduction to build profiles, this should work, but it doesn't seem to. I am using maven 2.0.8 was (Author: dragonfly0806): Here is an example project that demonstrates trying to load a build profile. According to the maven introduction to build profiles, this should work, but it doesn't seem to. > Profile activation based on hostname or IP > -- > > Key: MNG-3163 > URL: http://jira.codehaus.org/browse/MNG-3163 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Reporter: David J. M. Karlsen >Priority: Minor > Fix For: 3.x > > Attachments: exampleproject.zip > > > It would be very nice to be able to activate profiles based on hostname[s] or > IP-address[es]. > Yes, this could be exported from the system as a systemproperty quite easily > on *NIX with -Dhostname=`hostname` but is a little more tricky on other > platforms - so why not include it in maven itself? > It would be even better if it can be expressed with regex'es or the likes. > WDYT? -- 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-3882) Prevent local repository from also being the remote repository
[ http://jira.codehaus.org/browse/MNG-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156078#action_156078 ] Paul Benedict commented on MNG-3882: I want to compare the values of the local repo path and the remote repo path. I can set both of them to a file system path. I can't remember if I can do it directly, or use the file:// protocol. > Prevent local repository from also being the remote repository > -- > > Key: MNG-3882 > URL: http://jira.codehaus.org/browse/MNG-3882 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.0.10, 2.1.0-M1, 3.0-alpha-1 >Reporter: Paul Benedict > > User list shows that the local repository can be specified as a remote > repository. I've confirmed this is true. This is obviously a sore > misconfiguration. Let's check that the values are never equal. -- 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-3882) Prevent local repository from also being the remote repository
[ http://jira.codehaus.org/browse/MNG-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156079#action_156079 ] Paul Benedict commented on MNG-3882: Okay. I have verified I can put in the same exact value for both. Neither of them are using a protocol -- just a file system path. > Prevent local repository from also being the remote repository > -- > > Key: MNG-3882 > URL: http://jira.codehaus.org/browse/MNG-3882 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.0.10, 2.1.0-M1, 3.0-alpha-1 >Reporter: Paul Benedict > > User list shows that the local repository can be specified as a remote > repository. I've confirmed this is true. This is obviously a sore > misconfiguration. Let's check that the values are never equal. -- 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-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2261. --- Assignee: Carlos Sanchez Resolution: Fixed it' s going to be faster as all future releases go automatically to central > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee >Assignee: Carlos Sanchez > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- 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-2271) "net.objectlab.kit.datecalc","mavens...@shell.sourceforge.net:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin Jekot","mar...@users.sourceforge.n
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156088#action_156088 ] Carlos Sanchez commented on MAVENUPLOAD-2271: - unless you own objectlab.net your groupid should be net.sf.objectlabkit > "net.objectlab.kit.datecalc","[EMAIL > PROTECTED]:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin > Jekot","[EMAIL PROTECTED]",, > > > Key: MAVENUPLOAD-2271 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2271 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Marcin Jekot > -- 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-2253) Upload Joda-Time 1.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2253. --- Assignee: Carlos Sanchez Resolution: Fixed uploaded. Note that Maven 1 poms are no longer converted to Maven 2, so I have copied the 1.5.2 pom and changed the version. Please provide a Maven 2 pom from now on, you can get it from http://mirrors.ibiblio.org/pub/mirrors/maven2/joda-time/joda-time/1.5.2/joda-time-1.5.2.pom > Upload Joda-Time 1.6 > > > Key: MAVENUPLOAD-2253 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2253 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stephen Colebourne >Assignee: Carlos Sanchez > Attachments: pom.xml > > > http://joda-time.sourceforge.net/joda-time-1.6-bundle.jar > > http://joda-time.sourceforge.net > http://joda-time.sourceforge.net/team-list.html > > Please upload joda-time 1.6 -- 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-2250) Upload bundle for opensymhony.org's quartz scheduler
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156157#action_156157 ] Carlos Sanchez commented on MAVENUPLOAD-2250: - sorry, my mistake, you were right unfortunately I dont think it' s going to be a good idea to upload this without providing relocation poms for both quartz/quartz and opensymphony/quartz groups Adding a 3rd group would just be too confusing > Upload bundle for opensymhony.org's quartz scheduler > > > Key: MAVENUPLOAD-2250 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2250 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David J. M. Karlsen > Attachments: org.opensymphony.quartz.161.zip > > > Bundle attached as file upload -- 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-2248) Upload CGLIB 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2248. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload CGLIB 2.2 > > > Key: MAVENUPLOAD-2248 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2248 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > > http://www.people.apache.org/~joehni/cglib-nodep-2.2-bundle.jar > Links to two bundles for latest CGLIB versions 2.2. -- 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-2256) gwt-dnd upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2256. --- Assignee: Carlos Sanchez Resolution: Fixed > gwt-dnd upload request > -- > > Key: MAVENUPLOAD-2256 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2256 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Merijn de Jonge >Assignee: Carlos Sanchez > > http://www.extra.research.philips.com/hera/people/mdejonge/maven/gwt-dnd-2.5.6-bundle.jar > I'm a user, not a developer of the above package. > The gwt-dnd package is a newer version of gwt-dragdrop, which already exists > in the maven 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-2251) Aspectj 16.2. upload bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2251. --- Assignee: Carlos Sanchez Resolution: Fixed > Aspectj 16.2. upload bundle > --- > > Key: MAVENUPLOAD-2251 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2251 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > > Upload bundle for aspectj 1.6.2 -- 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-2259) JasperReports 3.1.2 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2259. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 3.1.2 upload > -- > > Key: MAVENUPLOAD-2259 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2259 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Teodor Danciu >Assignee: Carlos Sanchez > > http://jasperreports.sf.net/maven/jasperreports-3.1.2-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- 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-2259) JasperReports 3.1.2 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156158#action_156158 ] Carlos Sanchez commented on MAVENUPLOAD-2259: - removed the repositories section, please do it yourself for next releases > JasperReports 3.1.2 upload > -- > > Key: MAVENUPLOAD-2259 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2259 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Teodor Danciu >Assignee: Carlos Sanchez > > http://jasperreports.sf.net/maven/jasperreports-3.1.2-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- 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-2260) jetty-gwt upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2260. --- Assignee: Carlos Sanchez Resolution: Won't Fix jetty developers manage their section of the repo, you should ask them directly > jetty-gwt upload request > > > Key: MAVENUPLOAD-2260 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2260 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Merijn de Jonge >Assignee: Carlos Sanchez > > http://www.extra.research.philips.com/hera/people/mdejonge/maven/jetty-gwt-6.1.12-bundle.jar > I'm a user, not a developer of the above package. > This is an update to the newest version of the jetty-gwt package that works > with gwt-1.5.x. -- 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-2252) Upload bundle for opensymhony.org's quartz scheduler v1.6.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156159#action_156159 ] Carlos Sanchez commented on MAVENUPLOAD-2252: - unfortunately I dont think it' s going to be a good idea to upload this without providing relocation poms for both quartz/quartz and opensymphony/quartz groups Adding a 3rd group would just be too confusing > Upload bundle for opensymhony.org's quartz scheduler v1.6.2 > --- > > Key: MAVENUPLOAD-2252 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2252 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David J. M. Karlsen > > Bundle with sources, javadoc, poms and jars for v1.6.2 -- 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-2262) jewelcli sync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2262. --- Assignee: Carlos Sanchez Resolution: Fixed > jewelcli sync request > - > > Key: MAVENUPLOAD-2262 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2262 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Wood >Assignee: Carlos Sanchez > Attachments: mavensync > > > "uk.co.flamingpenguin.jewelcli","[EMAIL > PROTECTED]:/home/groups/j/je/jewelcli/htdocs/m2repo","rsync_ssh","Tim > Wood","[EMAIL PROTECTED]",, > http://webwhois.nic.uk/cgi-bin/whois.cgi?query=flamingpenguin.co.uk -- 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-2264) New Rsync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2264. --- Assignee: Carlos Sanchez Resolution: Fixed > New Rsync request > - > > Key: MAVENUPLOAD-2264 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2264 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kevin Menard >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-2265) Another new rsync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2265. --- Assignee: Carlos Sanchez Resolution: Won't Fix I' ve added com.servprise You dont need to add each subgroup > Another new rsync request > - > > Key: MAVENUPLOAD-2265 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2265 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kevin Menard >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-2267) rsync for appspy.org
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2267. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync for appspy.org > > > Key: MAVENUPLOAD-2267 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2267 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Olivier HEDIN >Assignee: Carlos Sanchez > > "org.appspy","[EMAIL PROTECTED]:/m2repo/releases","rsync_ssh","Olivier > HEDIN","[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-2270) NekoHTML 1.9.9 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156165#action_156165 ] Carlos Sanchez commented on MAVENUPLOAD-2270: - please read the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > NekoHTML 1.9.9 upload > - > > Key: MAVENUPLOAD-2270 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2270 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Eduardo > > http://downloads.sourceforge.net/nekohtml/nekohtml-1.9.9.zip -- 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-2268) Upload Barcode4J 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156163#action_156163 ] Carlos Sanchez commented on MAVENUPLOAD-2268: - thers is no www.people.apache.,org it is without the www I'm getting 403 forbidden anyway > Upload Barcode4J 2.0 > > > Key: MAVENUPLOAD-2268 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2268 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible > > http://www.people.apache.org/~joehni/barcode4j-fop-ext-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-complete-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-complete-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-light-2.0-bundle.jar > Note, there are already org.krysalis:barcode*:1.0beta1 artifacts. However, > those artifacts originate from the officially closed SF project > http://krysalis.sourceforge.net/ and the project has been moved to the SF > project barcode4j. Therefore the groupId in the new bundles is > net.sf.barcode4j. > Regards, > Jörg -- 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-2269) Ammentos Persistence Framework
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156164#action_156164 ] Carlos Sanchez commented on MAVENUPLOAD-2269: - please read the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Ammentos Persistence Framework > -- > > Key: MAVENUPLOAD-2269 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2269 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Davide Deidda > > Please upload 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: (MAVENUPLOAD-2272) upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156167#action_156167 ] Carlos Sanchez commented on MAVENUPLOAD-2272: - please read instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html > upload > --- > > Key: MAVENUPLOAD-2272 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2272 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Francois Fernandes > > another version of the svnkit library. -- 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-2189) Please setup synchronization for dbfit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156166#action_156166 ] Carlos Sanchez commented on MAVENUPLOAD-2189: - I'm sorry, but is this endorsed by fitnesse.org owners? or it' s an independent project? in the second case it should be in your own group (something like net.sf.dbfit) > Please setup synchronization for dbfit > -- > > Key: MAVENUPLOAD-2189 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2189 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pål Brattberg >Assignee: Carlos Sanchez > > "dbfit","[EMAIL > PROTECTED]://home/groups/d/db/dbfit/htdocs/m2repo/releases","rsync_ssh","Pal > Brattberg","[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] Closed: (MAVENUPLOAD-2273) Upload of jDatePicker to MVN central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2273. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload of jDatePicker to MVN central repo > - > > Key: MAVENUPLOAD-2273 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2273 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Juan Heyns >Assignee: Carlos Sanchez > > "net.sourceforge.jdatepicker","[EMAIL > PROTECTED]:/home/groups/j/jd/jdatepicker/htdocs/repo","rsync_ssh","Juan > Heyns","[EMAIL PROTECTED]",, > The project exists on sourceforge and I have set up a redirection page on > http://jdatepicker.sourceforge.net > which forwards to > http://www.pepperbytes.net/opensource/jdatepicker > from where my identity can be obtained if you click on contact. -- 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-2275) Sync ca.grimoire from its home at alchemy.grimoire.ca to central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2275. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync ca.grimoire from its home at alchemy.grimoire.ca to central > > > Key: MAVENUPLOAD-2275 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2275 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Owen Jacobson >Assignee: Carlos Sanchez > Attachments: central.csv > > > grimoire.ca hosts a number of freely-distributed (MIT-licensed) > "itch-scratching" projects. So that I can use them with a clean conscience in > for-hire work, I'd like to see them replicated to central. > The grimoire repository is being repopulated right now to remove > and elements and will be write-once from here on out. -- 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-2279) please sync org.bluestemsoftware
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156169#action_156169 ] Carlos Sanchez commented on MAVENUPLOAD-2279: - getting permission denied doing ssh [EMAIL PROTECTED] > please sync org.bluestemsoftware > > > Key: MAVENUPLOAD-2279 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2279 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: twayne > > http://www.networksolutions.com/whois/results.jsp?domain=bluestemsoftware.org -- 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-2283) Request for syncronization of repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2283. --- Assignee: Carlos Sanchez Resolution: Fixed > Request for syncronization of repository > > > Key: MAVENUPLOAD-2283 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2283 > Project: Maven Upload Requests > Issue Type: Wish > Components: Artifacts and Repositories >Reporter: Lars Helge Oeverland >Assignee: Carlos Sanchez > > "org.amplecode","[EMAIL > PROTECTED]:/var/www/amplecode/maven2","rsync_ssh","Lars Helge > Oeverland","[EMAIL PROTECTED]" > AmpleCode can be found at http://amplecode.org. My name can be found under > contacts at the front page. Your public key is added to the authorized keys. > Best regards, Lars Helge Øverland -- 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-2281) iText 2.1.4 released
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2281. --- Assignee: Carlos Sanchez Resolution: Fixed > iText 2.1.4 released > > > Key: MAVENUPLOAD-2281 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2281 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Xavier Le Vourch >Assignee: Carlos Sanchez > > iText 2.1.4 has been released. > You can download three different bundles from this URL: > http://itext.ugent.be/library/maven/ > http://itext.ugent.be/library/maven/itext-2.1.4-bundle.jar > http://itext.ugent.be/library/maven/itext-rtf-2.1.4-bundle.jar > http://itext.ugent.be/library/maven/itext-rups-2.1.4-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
[jira] Commented: (MAVENUPLOAD-2287) New opensource library (swing) to sync with central repository: JBusyComponent
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156170#action_156170 ] Carlos Sanchez commented on MAVENUPLOAD-2287: - proof of ownership of domain divxdede.org ? > New opensource library (swing) to sync with central repository: JBusyComponent > -- > > Key: MAVENUPLOAD-2287 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2287 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Christophe Lallement > > "org.divxdede","[EMAIL > PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","[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] Closed: (MAVENUPLOAD-2289) Upload maven-jetty-pluto-embedded 1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2289. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload maven-jetty-pluto-embedded 1.0.1 > --- > > Key: MAVENUPLOAD-2289 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2289 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Nils-Helge Garli >Assignee: Carlos Sanchez > > Please upload new version 1.0.1 of maven-jetty-pluto-embedded. -- 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-2288) "net.sf.twip","[EMAIL PROTECTED]/home/groups/t/tw/twip/htdocs/maven/repository","rsync_ssh","Snackbox","[EMAIL PROTECTED]",,
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2288. --- Assignee: Carlos Sanchez Resolution: Fixed > "net.sf.twip","[EMAIL > PROTECTED]/home/groups/t/tw/twip/htdocs/maven/repository","rsync_ssh","Snackbox","[EMAIL > PROTECTED]",, > - > > Key: MAVENUPLOAD-2288 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2288 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Snackbox >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] Commented: (MAVENUPLOAD-2286) nez sync rule from sourceforge project
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156172#action_156172 ] Carlos Sanchez commented on MAVENUPLOAD-2286: - proof of ownership of jvyami.org ? > nez sync rule from sourceforge project > -- > > Key: MAVENUPLOAD-2286 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2286 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Christophe Lallement > > "org.jvyaml","[EMAIL > PROTECTED]:/home/users/o/ou/ouaibsky/maven/m2repo","rsync_ssh","Ouaibsky","ouaibsky.free.fr",, -- 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-2291) Clover 2.4.2 core artifact upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156173#action_156173 ] Carlos Sanchez commented on MAVENUPLOAD-2291: - can you provide a Maven 2 pom in the bundle? we no longer conver Maven 1 poms you can get the previous one in http://repo1.maven.org/maven2/com/cenqua/clover/clover/2.4.1/clover-2.4.1.pom > Clover 2.4.2 core artifact upload request > - > > Key: MAVENUPLOAD-2291 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2291 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > > Please upload this to the maven1 repository. > Clover 2.4.2 for Maven has support for Clover's Test Optimization. > Clover is free for open source projects. -- 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-2292) maven1 clover2 plugin bundle upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156174#action_156174 ] Carlos Sanchez commented on MAVENUPLOAD-2292: - same thing here, would need a maven 2 pom, previous is at http://repo2.maven.org/maven2/maven/maven-clover-plugin/2.3.1/maven-clover-plugin-2.3.1.pom > maven1 clover2 plugin bundle upload > --- > > Key: MAVENUPLOAD-2292 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > > This is the actual maven1 plugin bundle - ready for deployment. > The new: > clover:test-optimize > goal, will run an optimized test set, depending on what tests hit what code > during the first full test run. -- 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-3884) Command line arguments don't overwrite settings.xml properties when invoking a plugin
Command line arguments don't overwrite settings.xml properties when invoking a plugin - Key: MNG-3884 URL: http://jira.codehaus.org/browse/MNG-3884 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.1.0-M1 Environment: All environments Reporter: laurent gousenbourger To explain the issue, let's start with the following example: 1°) Run a plugin goal with an argument specified in the command line with the "-D" option only mvn eclipse:eclipse -Declipse.projectNameTemplate=CommandLineProjectName We can see if we open the generated .project file that the name of the project is as we expect: "CommandLineProjectName" This is normal, the goal input parameter is set with the command line property. 2°) Run a plugin goal with an argument specified in the "settings.xml" file only mvn eclipse:eclipse with settings.xml containing the following enabled profile: testProfile SettingsProjectName testProfile We can see if we open the generated .project file that the name of the project is as we expect: "SettingsProjectName". This is normal, the input parameter of the goal is set with the "settings.xml" file property. 3°) Run a plugin goal with an argument specified in the command line with the "-D" option and with another value in the "settngs.xml" file If we use both scenarios, the property value set in the "settings.xml" file will overwrite the value set via the command line with the "-D" option. Maven should not react in that way but in the opposite: the command line value should overwite the "settings.xml" file value. It is already the case if we reuse the value somewhere in the pom.xml file. It should be the same when invoking a plugin goal. -- 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-3884) Command line arguments don't overwrite settings.xml properties when invoking a plugin
[ http://jira.codehaus.org/browse/MNG-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156177#action_156177 ] laurent gousenbourger commented on MNG-3884: The goal of that approach is to have default values configured in a profile of the settings.xml file. If we invoke different in-house plugins, the default values will be used. In special case, we would like to overwrite this default values by specifying them with the command line with thee "-D" option. In that case, the "-D" option should have the last word! > Command line arguments don't overwrite settings.xml properties when invoking > a plugin > - > > Key: MNG-3884 > URL: http://jira.codehaus.org/browse/MNG-3884 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1.0-M1 > Environment: All environments >Reporter: laurent gousenbourger > > To explain the issue, let's start with the following example: > 1°) Run a plugin goal with an argument specified in the command line with the > "-D" option only > mvn eclipse:eclipse -Declipse.projectNameTemplate=CommandLineProjectName > We can see if we open the generated .project file that the name of the > project is as we expect: "CommandLineProjectName" > This is normal, the goal input parameter is set with the command line > property. > 2°) Run a plugin goal with an argument specified in the "settings.xml" file > only > mvn eclipse:eclipse > with settings.xml containing the following enabled profile: > > > testProfile > > > SettingsProjectName > > > > > testProfile > > We can see if we open the generated .project file that the name of the > project is as we expect: "SettingsProjectName". > This is normal, the input parameter of the goal is set with the > "settings.xml" file property. > 3°) Run a plugin goal with an argument specified in the command line with the > "-D" option and with another value in the "settngs.xml" file > If we use both scenarios, the property value set in the "settings.xml" file > will overwrite the value set via the command line with the "-D" option. > Maven should not react in that way but in the opposite: the command line > value should overwite the "settings.xml" file value. > It is already the case if we reuse the value somewhere in the pom.xml file. > It should be the same when invoking a plugin goal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156178#action_156178
]
Benjamin Bentmann commented on MECLIPSE-414:
bq. Isn't that only if the CLI plugin isn't part of the normal lifecycle?
I don't fully get the meaning of those words. A plugin goal is either executed
directly from the CLI, i.e. via "mvn :", or indirectly from some
lifecycle, i.e. via "mvn " in combination with an {{}} from
the POM. That is to say, direct invocations from CLI are considered standalone
goal executions and are never part of any lifecycle.
bq. In this case m-eclipse-p is bound to the @phase generate-resources
What case exactly do you refer to? In the plugin's source code, i.e.
{{EclipsePlugin.java}}, I merely see [EMAIL PROTECTED]
phase="generate-resources"}} which has an entirely different semantic than the
similar looking [EMAIL PROTECTED] generate-resources}}. The first annotation
requests a forked execution, while the second annotations defines a default
phase if the goal is specified in an {{}} for which the user omitted
the {{}} element.
I mean for the case of executing "mvn eclipse:eclipse", the eclipse goal is not
bound to any lifecycle phase. No lifecycle phase, no other plugins unless the
goal explicitly requests a forked lifecylce/goal execution. That is why the
{{project}} variable does not see sources/resources that get dynamically
created/registered by other goals during the lifecycle.
Maybe that simplified flow can shed some light on this:
# "mvn eclipse:eclipse" is invoked by user
# {{MavenProject}} instance is build from POM, call this instance A
# lifecycle phase "generate-resources" is forked as per the eclipse goal's
[EMAIL PROTECTED] annotation
## {{MavenProject}} instance is build by cloning instance A, call this instance
B
## the lifecycle bound plugins are called, where their parameter expression
{{${project\}}} resolves to instance B, i.e. the plugins update instance B with
generated sources/resources
# Finally, the eclipse goal itself is executed, where {{${project}}} is
resolved with instance A and {{${executionProject}}} is resolved with instance B
If you like, have a look at {{DefaultLifecycleExecutor}} from the module
maven-core, that's where most of this process is handled.
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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-3163) Profile activation based on hostname or IP
[
http://jira.codehaus.org/browse/MNG-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156180#action_156180
]
Corporate Gadfly commented on MNG-3163:
---
You are using maven 2.0.8. Try it with 2.0.9. I'm using env.COMPUTERNAME to
trigger a profile. Here's a snippet which triggers when run on HOST1:
{code:xml}
env.COMPUTERNAME
HOST1
{code}
> Profile activation based on hostname or IP
> --
>
> Key: MNG-3163
> URL: http://jira.codehaus.org/browse/MNG-3163
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Reporter: David J. M. Karlsen
>Priority: Minor
> Fix For: 3.x
>
> Attachments: exampleproject.zip
>
>
> It would be very nice to be able to activate profiles based on hostname[s] or
> IP-address[es].
> Yes, this could be exported from the system as a systemproperty quite easily
> on *NIX with -Dhostname=`hostname` but is a little more tricky on other
> platforms - so why not include it in maven itself?
> It would be even better if it can be expressed with regex'es or the likes.
> WDYT?
--
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-355) Deploying from Leopard, with Svn 1.4.4 has error on automated Svn commit
[ http://jira.codehaus.org/browse/MRELEASE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156182#action_156182 ] benson margulies commented on MRELEASE-355: --- I just modified my POM to call for scm 1.1, and tried again, and got the same error. Can you give me any way to diagnose? > Deploying from Leopard, with Svn 1.4.4 has error on automated Svn commit > > > Key: MRELEASE-355 > URL: http://jira.codehaus.org/browse/MRELEASE-355 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: scm >Reporter: Paul Hammant >Assignee: Olivier Lamy > Fix For: 2.0-beta-8 > > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 3 minutes 25 seconds > [INFO] Finished at: Fri Jan 11 08:49:42 PST 2008 > [INFO] Final Memory: 14M/29M > [INFO] > > [INFO] Checking in modified POMs... > [INFO] Executing: svn --non-interactive commit --file > /tmp/maven-scm-1359802395.commit --targets /tmp/maven-scm-28211-targets > [INFO] Working directory: /scm/oss/jremoting/root/trunk > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: Commit failed (details follow): > svn: MKACTIVITY of > '/jremoting/!svn/act/c136e17a-8ec7-44c4-a326-b2611ec72ffc': authorization > failed (https://svn.codehaus.org) -- 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-2291) Clover 2.4.2 core artifact upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pellow updated MAVENUPLOAD-2291: - Attachment: clover-2.4.2-bundle.jar re-uploading bundle with the pom.xml included. > Clover 2.4.2 core artifact upload request > - > > Key: MAVENUPLOAD-2291 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2291 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > Attachments: clover-2.4.2-bundle.jar > > > Please upload this to the maven1 repository. > Clover 2.4.2 for Maven has support for Clover's Test Optimization. > Clover is free for open source projects. -- 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-2292) maven1 clover2 plugin bundle upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pellow updated MAVENUPLOAD-2292: - Attachment: maven-clover-plugin-2.4.2-bundle.jar re-uploading with pom.xml included > maven1 clover2 plugin bundle upload > --- > > Key: MAVENUPLOAD-2292 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > Attachments: maven-clover-plugin-2.4.2-bundle.jar > > > This is the actual maven1 plugin bundle - ready for deployment. > The new: > clover:test-optimize > goal, will run an optimized test set, depending on what tests hit what code > during the first full test run. -- 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-2292) maven1 clover2 plugin bundle upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156187#action_156187 ] Nick Pellow commented on MAVENUPLOAD-2292: -- Hi Carlos, Thanks for the heads-up on this. I've updated our release procedure for the plugin to include the pom.xml files for both the plugin, and the clover core artifact. Please let me know if there are any problems. Cheers, Nick > maven1 clover2 plugin bundle upload > --- > > Key: MAVENUPLOAD-2292 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > Attachments: maven-clover-plugin-2.4.2-bundle.jar > > > This is the actual maven1 plugin bundle - ready for deployment. > The new: > clover:test-optimize > goal, will run an optimized test set, depending on what tests hit what code > during the first full test run. -- 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-2292) maven1 clover2 plugin bundle upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pellow updated MAVENUPLOAD-2292: - Attachment: maven-clover-plugin-2.4.2-bundle.jar > maven1 clover2 plugin bundle upload > --- > > Key: MAVENUPLOAD-2292 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow > Attachments: maven-clover-plugin-2.4.2-bundle.jar, > maven-clover-plugin-2.4.2-bundle.jar > > > This is the actual maven1 plugin bundle - ready for deployment. > The new: > clover:test-optimize > goal, will run an optimized test set, depending on what tests hit what code > during the first full test run. -- 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: (MCOMPILER-85) Embedded error: Error while executing the compiler. com.sun.tools.javac.Main.compile([Ljava.lang.String;, java.io.PrintWriter)
[ http://jira.codehaus.org/browse/MCOMPILER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bahman Kalali closed MCOMPILER-85. -- Resolution: Not A Bug This turned out to be a problem on our side using a corrupted JDK 1.5.0_16. For some reasons the tools.jar that we had in JDK 1.5.0_16 was corrupted. The Main.compile(String, PrintWriter) was missing in tools.jar of in JDK 1.5.0_16. We re-installed the latest JDK 1.5.0_16 and everything worked fine. > Embedded error: Error while executing the compiler. > com.sun.tools.javac.Main.compile([Ljava.lang.String;, java.io.PrintWriter) > -- > > Key: MCOMPILER-85 > URL: http://jira.codehaus.org/browse/MCOMPILER-85 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Java(TM) 2 Runtime Environment, Standard Edition (build > 1.5.0_16-b02) > apache-maven-2.0.9 > Windows XP V2002 Service Pack 3 >Reporter: Bahman Kalali > > When I run "mvn install -e" on a war application, I am getting the following > exception: > [INFO] Fatal error compiling > Embedded error: Error while executing the compiler. > com.sun.tools.javac.Main.compile([Ljava.lang.String;, java.io.PrintWriter) > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Fatal error compiling > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.j > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecyc > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.ja > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLif > ) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExe > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:1 > 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.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error > compiling > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:498) > at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.j > ... 16 more > Caused by: org.codehaus.plexus.compiler.CompilerException: Error while > executing the compiler. > at > org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:426) > at > org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141) > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493) > ... 19 more > Caused by: java.lang.NoSuchMethodException: > com.sun.tools.javac.Main.compile([Ljava.lang.String;, java > at java.lang.Class.getMethod(Class.java:1581) > at > org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:418) > It looks like the compiler is calling > com.sun.tools.javac.Main.compile([Ljava.lang.String;, java.io.PrintWriter) > where the 1.5.0_16-b02 supports only java.lang.NoSuchMethodException: > com.sun.tools.javac.Main.compile([Ljava.lang.String) method. > Best regards, > --Bahman -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-414.
---
Resolution: Not A Bug
As per Benjamin Bentmann's comments; the eclipse plugin being run from the CLI
will never have access to other plugins unless run via @execute.
Therefore can't removed executedProject as this is the result of the forked
lifecycle which contains the information we want.
Marking as not a bug.
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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-3822) POM interpolation does not use basedir-aligned build directories
[
http://jira.codehaus.org/browse/MNG-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell closed MNG-3822.
-
Resolution: Fixed
Fixed.
> POM interpolation does not use basedir-aligned build directories
>
>
> Key: MNG-3822
> URL: http://jira.codehaus.org/browse/MNG-3822
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Assignee: Shane Isbell
> Fix For: 3.0-alpha-1
>
>
> During POM interpolation, (some) expressions referring to build directories
> are replaced with relative paths. E.g. {{${project.build.outputDirectory}}}
> only yields {{target/classes}}. This can affect plugins when these
> expressions are used to interpolate the project properties and plugins (like
> Resources or Invoker) use the project properties to filter further 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] Updated: (MNG-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account
[
http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell updated MNG-3848:
--
Fix Version/s: 3.0-alpha-2
> Inheritance of project/site/scm URLs does not take child's relative location
> to parent into account
> ---
>
> Key: MNG-3848
> URL: http://jira.codehaus.org/browse/MNG-3848
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-2
>
>
> For a multi-module layout like
> {noformat}
> parent/
> pom.xml
> child/
> pom.xml
> {noformat}
> and a project URL like "http://foo.org/parent"; inherited from the parent, the
> child is expected to end up with the URL "http://foo.org/child"; instead of
> "http://foo.org/parent/child";, i.e. the child's relative location to the
> parent should be considered during inheritance.
--
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-2268) Upload Barcode4J 2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156202#action_156202 ] Joerg Schaible commented on MAVENUPLOAD-2268: - Don't know why it is always so difficult to publish some bundles without making any mistake . All corrected links again for your convenience (rights have been fixed): http://people.apache.org/~joehni/barcode4j-2.0-bundle.jar http://people.apache.org/~joehni/barcode4j-fop-ext-2.0-bundle.jar http://people.apache.org/~joehni/barcode4j-fop-ext-complete-2.0-bundle.jar http://people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-2.0-bundle.jar http://people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-complete-2.0-bundle.jar http://people.apache.org/~joehni/barcode4j-light-2.0-bundle.jar Thanks, Jörg > Upload Barcode4J 2.0 > > > Key: MAVENUPLOAD-2268 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2268 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible > > http://www.people.apache.org/~joehni/barcode4j-fop-ext-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-complete-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-fop-ext-0.20.5-complete-2.0-bundle.jar > http://www.people.apache.org/~joehni/barcode4j-light-2.0-bundle.jar > Note, there are already org.krysalis:barcode*:1.0beta1 artifacts. However, > those artifacts originate from the officially closed SF project > http://krysalis.sourceforge.net/ and the project has been moved to the SF > project barcode4j. Therefore the groupId in the new bundles is > net.sf.barcode4j. > Regards, > Jörg -- 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-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account
[
http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell closed MNG-3848.
-
Resolution: Won't Fix
Fix Version/s: (was: 3.0-alpha-2)
3.0-alpha-1
We had a discussion a while back about not using module names in 3.0 for the
URLs, but instead using the artifact id (project name) appended to the URL. So
this is a change of behavior.
> Inheritance of project/site/scm URLs does not take child's relative location
> to parent into account
> ---
>
> Key: MNG-3848
> URL: http://jira.codehaus.org/browse/MNG-3848
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-1
>
>
> For a multi-module layout like
> {noformat}
> parent/
> pom.xml
> child/
> pom.xml
> {noformat}
> and a project URL like "http://foo.org/parent"; inherited from the parent, the
> child is expected to end up with the URL "http://foo.org/child"; instead of
> "http://foo.org/parent/child";, i.e. the child's relative location to the
> parent should be considered during inheritance.
--
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-3819) Plugins that don't declare dependency on plexus-utils no longer get plexus-utils:1.1
[ http://jira.codehaus.org/browse/MNG-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3819: -- Affects Version/s: (was: 3.0-alpha-1) 3.0-alpha-3 > Plugins that don't declare dependency on plexus-utils no longer get > plexus-utils:1.1 > > > Key: MNG-3819 > URL: http://jira.codehaus.org/browse/MNG-3819 > Project: Maven 2 > Issue Type: Bug > Components: Class Loading, Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > > To compensate for MNG-2892, Maven 2.0.6+ automatically injects > plexus-utils:1.1 into the plugin class realm if the plugin POM does not > declare a (direct) dependency on plexus-utils:1.1+. This backward-compat mode > is currently not existent in Maven 3.x. > Even if this break is intentional for 3.x, this issue allows to track 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] Updated: (MNG-3819) Plugins that don't declare dependency on plexus-utils no longer get plexus-utils:1.1
[ http://jira.codehaus.org/browse/MNG-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3819: -- Affects Version/s: (was: 3.0-alpha-3) 3.0-alpha-1 Fix Version/s: 3.0-alpha-3 > Plugins that don't declare dependency on plexus-utils no longer get > plexus-utils:1.1 > > > Key: MNG-3819 > URL: http://jira.codehaus.org/browse/MNG-3819 > Project: Maven 2 > Issue Type: Bug > Components: Class Loading, Plugins and Lifecycle >Affects Versions: 3.0-alpha-1 >Reporter: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > > To compensate for MNG-2892, Maven 2.0.6+ automatically injects > plexus-utils:1.1 into the plugin class realm if the plugin POM does not > declare a (direct) dependency on plexus-utils:1.1+. This backward-compat mode > is currently not existent in Maven 3.x. > Even if this break is intentional for 3.x, this issue allows to track 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] Closed: (MNG-3829) 3.0-alpha-1 release: get the core ITs passing
[ http://jira.codehaus.org/browse/MNG-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3829. - Resolution: Fixed > 3.0-alpha-1 release: get the core ITs passing > - > > Key: MNG-3829 > URL: http://jira.codehaus.org/browse/MNG-3829 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Brian Fox >Assignee: Shane Isbell > Fix For: 3.0-alpha-1 > > > All core ITs must be passing with the 3.0-alpha-1 code -- 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
