[jira] Commented: (MECLIPSE-377) eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than once in a multi-project
[ http://jira.codehaus.org/browse/MECLIPSE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157218#action_157218 ] Joerg Schaible commented on MECLIPSE-377: - Thanks Barrie, this is great news! - Jörg > eclipse:eclipse -DdownloadSources=true shouldn't attempt download more than > once in a multi-project > --- > > Key: MECLIPSE-377 > URL: http://jira.codehaus.org/browse/MECLIPSE-377 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath), Core : Multi-projects >Affects Versions: 2.4 >Reporter: Steinar Bang >Assignee: Barrie Treloar > Fix For: 2.6 > > > If you run "mvn eclipse:eclipse -DdownloadSources=true" it attempts to > download source jars for all projects, even when it has tried (and failed) to > download the jars in earlier projects. This slows down the goal a lot on > slow network connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3875) Make sure Tycho builds with Maven 3.0.x
[ http://jira.codehaus.org/browse/MNG-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3875. -- Resolution: Fixed We needed to add the maven-compat module to the artifact filter and then all was good with Tycho. > Make sure Tycho builds with Maven 3.0.x > --- > > Key: MNG-3875 > URL: http://jira.codehaus.org/browse/MNG-3875 > Project: Maven 2 > Issue Type: Bug >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] Commented: (MNG-3719) Need to have a way to either define plugin execution dependencies on other plugin executions having executed first (at least within same lifecycle phase)
[
http://jira.codehaus.org/browse/MNG-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157222#action_157222
]
Sandra Bogaert commented on MNG-3719:
-
Hi,
What about this issue ?
Do you have a release date ?
Thanks in advance
> Need to have a way to either define plugin execution dependencies on other
> plugin executions having executed first (at least within same lifecycle phase)
> -
>
> Key: MNG-3719
> URL: http://jira.codehaus.org/browse/MNG-3719
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.9
> Environment: Maven 2.0.9, java version "1.5.0_13" Java(TM) 2 Runtime
> Environment, Standard Edition (build 1.5.0_13-b05-241) Java HotSpot(TM)
> Client VM (build 1.5.0_13-120, mixed mode, sharing), OS X 10.4
>Reporter: Gary S. Weaver
>Priority: Critical
> Attachments: plugin-execution-order-cant-be-defined-maven-2.0.9.tar.gz
>
>
> I extend my sincere apologies if there is a much easier way of doing this,
> but so far I haven't found any.
> There should be some way to ensure order of plugin executions through
> dependencies on other executions. See attached project for example, or see
> below for the applicable example in a pom.xml. When plugins are defined in
> pom.xml in the following manner to ensure correct execution order, they are
> not executed sequentially and there is no way to indicate dependencies, as
> would be expected (note- I'm not expecting that it interpret the "step 1...",
> ..., "step 5..." IDs, I'm only suggesting that either the plugins be executed
> in order that they are found in the XML (most intuitive) or that there be
> some concept of priority/ordinal added, or even perhaps (this would be most
> "ant-like") that plugin executions (and maybe even plugin goal executions) be
> allowed to define prequisite execution IDs to be run (even if they are IDs
> not defined in the pom, but maybe a parent pom, even though I don't need that
> right now).
> I know that this could be problematic if a plugin execution from one
> lifecycle phase depends on another from another lifecycle phase (and you
> could get into circular references that way that would have to be recognized
> during pom validation after loading/merging pom.xmls). However, not being
> able to at the very least define order of execution of different (or the
> same) plugin executions as noted below and in attached project makes it
> difficult to chain plugin executions that depend on each other, thereby
> reducing the practicality of the pom.xml and Maven 2.
> For example, these plugin executions cannot be ordered properly in Maven
> 2.0.9, since there appears to be no way to indicate dependencies of one
> execution on another:
> {code}
>
>
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.5
> 1.5
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> step 1 - backup-original-web.xml-from-src
> generate-resources
>
> run
>
>
>
>
>
> file="${pom.basedir}/src/main/webapp/WEB-INF/web.xml"
> todir="${pom.basedir}/target/tmpwebxml/"/>
>
>
>
>
>
>
>
> org.codehaus.mojo
> jspc-maven-plugin
>
>
> step 2 - jspc
> generate-resources
>
> compile
>
>
>
>
>
>
>
>
>
> org.apache.pluto
> pluto-taglib
> 1.1.3
> jar
>
>
> javax.portlet
> portlet-api
> 1.0
> jar
>
>
> javax.servlet
> jstl
>
[jira] Issue Comment Edited: (MSITE-169) links to modules where not working if a modules dir is used
[ http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155199#action_155199 ] alexandr kiryanov edited comment on MSITE-169 at 12/8/08 7:58 AM: -- The problem still exists for 2.0-beta-7 version. MNG-MSITE-169-maven-site-plugin.patch was manually applied for 2.0-beta-7 version and then generated new patch. Use it if you want to fix described problem for 2.0-beta-7 version. This patch fixes problems described above but unfortunately it makes problems for links that were correct :( was (Author: alexandr.kiryanov): The problem still exists for 2.0-beta-7 version. MNG-MSITE-169-maven-site-plugin.patch was manually applied for 2.0-beta-7 version and then generated new patch. Use it if you want to fix described problem for 2.0-beta-7 version. > links to modules where not working if a modules dir is used > --- > > Key: MSITE-169 > URL: http://jira.codehaus.org/browse/MSITE-169 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 >Reporter: Mathias Brökelmann > Attachments: 169-maven-site-plugin-for-2.0-beta-7.patch, > MNG-MSITE-169-maven-site-plugin.patch, MSITE-169.zip > > > I've to place the modules into a separate directory: > root/ > ..pom.xml > ..modules/ > module1 > module2 > this is supported by maven through > > modules/module1 > modules/module2 > > in pom. > but the site generation seems to be broken: > if mvn site-deploy is used the links to the modules contain > modules/module1/index.html which is ok but unfortunately the generated site > structure will be generated as follows: > root/ > ..module1 > ..module2 > The result is that the links do not work. > If I run mvn site-stage everything looks ok. The links doesn't contain > modules dir anymore and eveything is working. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3893) Maven2 is looking for updates on available final artifacts
Maven2 is looking for updates on available final artifacts -- Key: MNG-3893 URL: http://jira.codehaus.org/browse/MNG-3893 Project: Maven 2 Issue Type: Bug Environment: any Reporter: Stefan Franke Maven2 is looking for updates on available final artifacts, which are artifacts without a SNAPSHOT version. If version numbers have any meaning then there must not exist different artifacts for groupId/artifactId/version. And if there can be only an unique artifact it is wrong to search for updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3894) provide an include mechanism to include other pom.xml
provide an include mechanism to include other pom.xml - Key: MNG-3894 URL: http://jira.codehaus.org/browse/MNG-3894 Project: Maven 2 Issue Type: Improvement Components: Inheritance and Interpolation Environment: any Reporter: Stefan Franke The idea to manage project independent templates is not new. But it is not possible to do this with maven and neither inheritance nor the dependency mechanism is enough. The include mechnism would include the requested pom (including ist parent poms) as if the containing elements where part of the current pom. Thus allowing to use every available pom mechanism. On conflict local pom settings wins. Very useful and needed to reduce redundancy between different 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: (MNG-3893) Maven2 is looking for updates on available final artifacts
[ http://jira.codehaus.org/browse/MNG-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157255#action_157255 ] Wendy Smoak commented on MNG-3893: -- Please post the build output that prompted you to open this issue. How did these artifacts get into the repo? (My guess is that it's looking for poms, not the jars.) Another thing to check is your repository update policies. It is possible to configure Maven to check for updates on releases, but it doesn't happen by default. > Maven2 is looking for updates on available final artifacts > -- > > Key: MNG-3893 > URL: http://jira.codehaus.org/browse/MNG-3893 > Project: Maven 2 > Issue Type: Bug > Environment: any >Reporter: Stefan Franke > > Maven2 is looking for updates on available final artifacts, which are > artifacts without a SNAPSHOT version. > If version numbers have any meaning then there must not exist different > artifacts for groupId/artifactId/version. > And if there can be only an unique artifact it is wrong to search for updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3893) Maven2 is looking for updates on available final artifacts
[ http://jira.codehaus.org/browse/MNG-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157257#action_157257 ] Stefan Franke commented on MNG-3893: shame on me. you are right. Someone "tuned" our repo server... thanks for that hint. Closing this. > Maven2 is looking for updates on available final artifacts > -- > > Key: MNG-3893 > URL: http://jira.codehaus.org/browse/MNG-3893 > Project: Maven 2 > Issue Type: Bug > Environment: any >Reporter: Stefan Franke > > Maven2 is looking for updates on available final artifacts, which are > artifacts without a SNAPSHOT version. > If version numbers have any meaning then there must not exist different > artifacts for groupId/artifactId/version. > And if there can be only an unique artifact it is wrong to search for updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3893) Maven2 is looking for updates on available final artifacts
[ http://jira.codehaus.org/browse/MNG-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Franke closed MNG-3893. -- Resolution: Not A Bug > Maven2 is looking for updates on available final artifacts > -- > > Key: MNG-3893 > URL: http://jira.codehaus.org/browse/MNG-3893 > Project: Maven 2 > Issue Type: Bug > Environment: any >Reporter: Stefan Franke > > Maven2 is looking for updates on available final artifacts, which are > artifacts without a SNAPSHOT version. > If version numbers have any meaning then there must not exist different > artifacts for groupId/artifactId/version. > And if there can be only an unique artifact it is wrong to search for updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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=157263#action_157263 ] Pål Brattberg commented on MAVENUPLOAD-2189: net.sf.dbfit is fine, we'll go with that. Thanks! "net.sf.dbfit","[EMAIL PROTECTED]://home/groups/d/db/dbfit/htdocs/m2repo/releases","rsync_ssh","Pal Brattberg","[EMAIL PROTECTED]",, > 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] Created: (MAVENUPLOAD-2298) Please setup synchronization for webtestfixtures
Please setup synchronization for webtestfixtures Key: MAVENUPLOAD-2298 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2298 Project: Maven Upload Requests Issue Type: Wish Reporter: Pål Brattberg "net.sf.webtestfixtures","[EMAIL PROTECTED]://home/groups/w/we/webtestfixtures/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] Created: (MERCURY-48) Document and vet the design
Document and vet the design --- Key: MERCURY-48 URL: http://jira.codehaus.org/browse/MERCURY-48 Project: Mercury Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2299) FitNesse and FitLibrary 20081201
FitNesse and FitLibrary 20081201 Key: MAVENUPLOAD-2299 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2299 Project: Maven Upload Requests Issue Type: Wish Reporter: Pål Brattberg FitNesse is a fully integrated standalone wiki and acceptance testing framework using FIT. FitLibrary is an extension for FIT/FitNesse I'm not a developer of FitNesse, but I am for DbFit and WebTestFixtures which are dependant on FitNesse. The official JAR's are found at: http://www.fitnesse.org/FitNesse.DownLoad The JAR's packaged for Maven (with POM) are found at: http://julafton.com/fitnesse/fitnesse-20081201-bundle.jar http://julafton.com/fitnesse/fitlibrary-20081201-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] Updated: (MERCURY-48) Document and vet the design
[ http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-48: Component/s: Ant tasks > Document and vet the design > --- > > Key: MERCURY-48 > URL: http://jira.codehaus.org/browse/MERCURY-48 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-10) wrap Mercury into Ant tasks
[ http://jira.codehaus.org/browse/MERCURY-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-10: Component/s: (was: Misc/All) Ant tasks > wrap Mercury into Ant tasks > --- > > Key: MERCURY-10 > URL: http://jira.codehaus.org/browse/MERCURY-10 > Project: Mercury > Issue Type: New Feature > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > > * allow ant builds use Mercury for binary retrieval/storage > * add real artifact resolution when available in Mercury > * try out dependency separation alternatives (separation from POM) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MERCURY-49) Implement basic classpath functionality
Implement basic classpath functionality --- Key: MERCURY-49 URL: http://jira.codehaus.org/browse/MERCURY-49 Project: Mercury Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-49) Implement basic classpath functionality
[ http://jira.codehaus.org/browse/MERCURY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-49: Description: basics: ability to: * configure repositories * declare dependencies * resolve classpath Component/s: Ant tasks > Implement basic classpath functionality > --- > > Key: MERCURY-49 > URL: http://jira.codehaus.org/browse/MERCURY-49 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > > basics: ability to: > * configure repositories > * declare dependencies > * resolve classpath -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-50) Implement repository writing functionality
Implement repository writing functionality -- Key: MERCURY-50 URL: http://jira.codehaus.org/browse/MERCURY-50 Project: Mercury Issue Type: Sub-task Reporter: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-51) Implement reading dependencies from a POM
Implement reading dependencies from a POM -- Key: MERCURY-51 URL: http://jira.codehaus.org/browse/MERCURY-51 Project: Mercury Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-48) Document and vet the design
[ http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-48: Remaining Estimate: 2 days Original Estimate: 2 days > Document and vet the design > --- > > Key: MERCURY-48 > URL: http://jira.codehaus.org/browse/MERCURY-48 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-50) Implement repository writing functionality
[ http://jira.codehaus.org/browse/MERCURY-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-50: Remaining Estimate: 2 days Original Estimate: 2 days > Implement repository writing functionality > -- > > Key: MERCURY-50 > URL: http://jira.codehaus.org/browse/MERCURY-50 > Project: Mercury > Issue Type: Sub-task >Reporter: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-49) Implement basic classpath functionality
[ http://jira.codehaus.org/browse/MERCURY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-49: Remaining Estimate: 2 days Original Estimate: 2 days > Implement basic classpath functionality > --- > > Key: MERCURY-49 > URL: http://jira.codehaus.org/browse/MERCURY-49 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > > basics: ability to: > * configure repositories > * declare dependencies > * resolve classpath -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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 started: (MERCURY-48) Document and vet the design
[ http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MERCURY-48 started by Oleg Gusakov. > Document and vet the design > --- > > Key: MERCURY-48 > URL: http://jira.codehaus.org/browse/MERCURY-48 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-50) Implement repository writing functionality
[ http://jira.codehaus.org/browse/MERCURY-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-50: Assignee: Oleg Gusakov > Implement repository writing functionality > -- > > Key: MERCURY-50 > URL: http://jira.codehaus.org/browse/MERCURY-50 > Project: Mercury > Issue Type: Sub-task >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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=157273#action_157273 ] Carlos Sanchez commented on MAVENUPLOAD-2291: - this one is solved, the maven 1 plugin has a little bit of trouble, will comment in MAVENUPLOAD-2292 > 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 >Assignee: Carlos Sanchez > 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] 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=157275#action_157275 ] Carlos Sanchez commented on MAVENUPLOAD-2292: - rigth now everything in the com.atlassian groupId is being automatically synced the problem is that the maven 1 plugin is in the maven group. I have uploaded by hand this time, maybe there' s a way to automate it in the future > 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] Updated: (MERCURY-50) Implement repository writing functionality
[ http://jira.codehaus.org/browse/MERCURY-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-50: Component/s: Ant tasks > Implement repository writing functionality > -- > > Key: MERCURY-50 > URL: http://jira.codehaus.org/browse/MERCURY-50 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-50) Implement repository writing functionality
[ http://jira.codehaus.org/browse/MERCURY-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-50: Description: Install / deploy functionality > Implement repository writing functionality > -- > > Key: MERCURY-50 > URL: http://jira.codehaus.org/browse/MERCURY-50 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > > Install / deploy functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-51) Implement reading dependencies from a POM
[ http://jira.codehaus.org/browse/MERCURY-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-51: Component/s: Ant tasks > Implement reading dependencies from a POM > -- > > Key: MERCURY-51 > URL: http://jira.codehaus.org/browse/MERCURY-51 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-52) UTs sometimes hang, clean & second run fixes it
UTs sometimes hang, clean & second run fixes it --- Key: MERCURY-52 URL: http://jira.codehaus.org/browse/MERCURY-52 Project: Mercury Issue Type: Bug Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-52) UTs sometimes hang, clean & second run fixes it
[
http://jira.codehaus.org/browse/MERCURY-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157292#action_157292
]
Oleg Gusakov commented on MERCURY-52:
-
IgorF:
{quote}
the hang seems to be reproducible. I killed org/apache/maven/mercury from my
local repo and the build is stuck again
{quote}
{code}
Running org.apache.maven.mercury.spi.http.client.SecureJettyDeployerTest
2008-12-08 14:22:36.109::INFO: jetty-6.1.12
2008-12-08 14:22:36.213::INFO: Started [EMAIL PROTECTED]:35759
Basedir = /tmp/deployerTestFiles27948.tmp
Destroyed /tmp/deployerTestFiles27948.tmp
2008-12-08 14:22:36.534::INFO: jetty-6.1.12
2008-12-08 14:22:36.536::INFO: Started [EMAIL PROTECTED]:58250
{code}
> UTs sometimes hang, clean & second run fixes it
> ---
>
> Key: MERCURY-52
> URL: http://jira.codehaus.org/browse/MERCURY-52
> Project: Mercury
> Issue Type: Bug
>Reporter: Oleg Gusakov
>Assignee: Oleg Gusakov
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MERCURY-52) UTs sometimes hang, clean & second run fixes it
[ http://jira.codehaus.org/browse/MERCURY-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157297#action_157297 ] Igor Fedorenko commented on MERCURY-52: --- This appears to happen rather frequently on ubuntu 8.10 x86_64 and sun jdk 1.5.0_16 even without cleaning local repository. > UTs sometimes hang, clean & second run fixes it > --- > > Key: MERCURY-52 > URL: http://jira.codehaus.org/browse/MERCURY-52 > Project: Mercury > Issue Type: Bug >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-48) Document and vet the design
[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157315#action_157315
]
Oleg Gusakov commented on MERCURY-48:
-
The proposed syntax looks like this
{code:xml | title=build.xml | borderStyle=solid }
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
> Document and vet the design
> ---
>
> Key: MERCURY-48
> URL: http://jira.codehaus.org/browse/MERCURY-48
> Project: Mercury
> Issue Type: Sub-task
> Components: Ant tasks
>Reporter: Oleg Gusakov
>Assignee: Oleg Gusakov
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MERCURY-53) implement reading configuration from settings.xml
implement reading configuration from settings.xml - Key: MERCURY-53 URL: http://jira.codehaus.org/browse/MERCURY-53 Project: Mercury Issue Type: Sub-task Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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 started: (MERCURY-49) Implement basic classpath functionality
[ http://jira.codehaus.org/browse/MERCURY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MERCURY-49 started by Oleg Gusakov. > Implement basic classpath functionality > --- > > Key: MERCURY-49 > URL: http://jira.codehaus.org/browse/MERCURY-49 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > > basics: ability to: > * configure repositories > * declare dependencies > * resolve classpath -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MERCURY-48) Document and vet the design
[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157315#action_157315
]
Oleg Gusakov edited comment on MERCURY-48 at 12/8/08 3:11 PM:
--
The proposed syntax looks like this
{code:xml|title=build.xml|borderStyle=solid}
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
was (Author: olle):
The proposed syntax looks like this
{code:xml | title=build.xml | borderStyle=solid }
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
> Document and vet the design
> ---
>
> Key: MERCURY-48
> URL: http://jira.codehaus.org/browse/MERCURY-48
> Project: Mercury
> Issue Type: Sub-task
> Components: Ant tasks
>Reporter: Oleg Gusakov
>Assignee: Oleg Gusakov
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MERCURY-48) Document and vet the design
[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157315#action_157315
]
Oleg Gusakov edited comment on MERCURY-48 at 12/8/08 3:11 PM:
--
The proposed syntax looks like this
{code:xml|title=build.xml|borderStyle=solid}
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
was (Author: olle):
The proposed syntax looks like this
{code:xml|title=build.xml|borderStyle=solid}
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
> Document and vet the design
> ---
>
> Key: MERCURY-48
> URL: http://jira.codehaus.org/browse/MERCURY-48
> Project: Mercury
> Issue Type: Sub-task
> Components: Ant tasks
>Reporter: Oleg Gusakov
>Assignee: Oleg Gusakov
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (MERCURY-48) Document and vet the design
[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157315#action_157315
]
Oleg Gusakov edited comment on MERCURY-48 at 12/8/08 3:15 PM:
--
The proposed syntax looks like this
{code:xml|title=build.xml|borderStyle=solid}
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
was (Author: olle):
The proposed syntax looks like this
{code:xml|title=build.xml|borderStyle=solid}
http://repo1.maven.org/maven2"/>
http://localhost:8081/nexus/contents/groups/public"/>
http://maven.apache.org/mercury/1"/>
{code}
> Document and vet the design
> ---
>
> Key: MERCURY-48
> URL: http://jira.codehaus.org/browse/MERCURY-48
> Project: Mercury
> Issue Type: Sub-task
> Components: Ant tasks
>Reporter: Oleg Gusakov
>Assignee: Oleg Gusakov
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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=157324#action_157324 ] Nick Pellow commented on MAVENUPLOAD-2292: -- thanks Carlos. Please let me know if there is anything we can do to help automate this in the future. 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, > 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: (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 closed MAVENUPLOAD-2292. Resolution: Fixed > 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] Commented: (MJAVADOC-214) test javadoc goal uses incorrect dependency classpath
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157330#action_157330 ] Christian Decker commented on MJAVADOC-214: --- How would you do that? > test javadoc goal uses incorrect dependency classpath > - > > Key: MJAVADOC-214 > URL: http://jira.codehaus.org/browse/MJAVADOC-214 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Brett Porter > > according to this report: > http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html > The test javadoc goal is not using the test classpath dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSHADE-42) Reactor builds do not use shaded jar
[ http://jira.codehaus.org/browse/MSHADE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay updated MSHADE-42: -- Attachment: MSHADE-42.patch This problem exists because the target/classes directory is specified as the project compile classpath instead of the built jar. Patch moves target/classes to target/original-classses and unpacks the newly shaded jar in its place. > Reactor builds do not use shaded jar > > > Key: MSHADE-42 > URL: http://jira.codehaus.org/browse/MSHADE-42 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Dave Meibusch > Attachments: MSHADE-42.patch > > > I have a multi-module project with several of the modules using shade to > create uber jars. > One the modules depends on an uber jar module. When doing a reactor build, > this module is built with a compile classpath containing: >/xxx/yyy/uberjar-module/target/classes > rather than the shaded uber jar created (and installed) earlier in the > reactor build. > When the module is built alone, the dependency in the compile classpath is > correctly the shaded jar in the local repository. > I don't know enough about the internals of reactor builds to determine if > this is a deficiency of the shade plugin or Maven's reactor mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-508) If base artifact does not exist unavailable cache incorrectly updated
If base artifact does not exist unavailable cache incorrectly updated - Key: MECLIPSE-508 URL: http://jira.codehaus.org/browse/MECLIPSE-508 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.5.1 Reporter: Barrie Treloar If the requested dependency does not exist the unavailable cache would also get updated. This could occur if you made a typo in dependencies. With the change to marker files in MECLIPSE-377 this caused errors because the marker files would be created in non existent directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-508) If base artifact does not exist unavailable cache incorrectly updated
[ http://jira.codehaus.org/browse/MECLIPSE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-508. --- Resolution: Fixed Fix Version/s: 2.6 > If base artifact does not exist unavailable cache incorrectly updated > - > > Key: MECLIPSE-508 > URL: http://jira.codehaus.org/browse/MECLIPSE-508 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Barrie Treloar > Fix For: 2.6 > > > If the requested dependency does not exist the unavailable cache would also > get updated. > This could occur if you made a typo in dependencies. > With the change to marker files in MECLIPSE-377 this caused errors because > the marker files would be created in non existent directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-508) If base artifact does not exist then the unavailable cache was incorrectly updated
[ http://jira.codehaus.org/browse/MECLIPSE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar updated MECLIPSE-508: Summary: If base artifact does not exist then the unavailable cache was incorrectly updated (was: If base artifact does not exist unavailable cache incorrectly updated) > If base artifact does not exist then the unavailable cache was incorrectly > updated > -- > > Key: MECLIPSE-508 > URL: http://jira.codehaus.org/browse/MECLIPSE-508 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Barrie Treloar >Assignee: Barrie Treloar > Fix For: 2.6 > > > If the requested dependency does not exist the unavailable cache would also > get updated. > This could occur if you made a typo in dependencies. > With the change to marker files in MECLIPSE-377 this caused errors because > the marker files would be created in non existent directories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-509) Unavailable cache is incorrectly updated to mark sources/javadoc as not available when downloads option is not specified
Unavailable cache is incorrectly updated to mark sources/javadoc as not available when downloads option is not specified Key: MECLIPSE-509 URL: http://jira.codehaus.org/browse/MECLIPSE-509 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.5.1 Reporter: Barrie Treloar If downloadSources is not specified and the source jar does not already exist in the local repository then the unavailable cache was incorrectly updated to indicate that the source for this artifact did not exist. Updating the unavailable cache can only be done if the artifact was resolved against the remote repositories (which requires downloadSources=true) Similarly for downloadJavadocs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-509) Unavailable cache is incorrectly updated to mark sources/javadoc as not available when downloads option is not specified
[ http://jira.codehaus.org/browse/MECLIPSE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MECLIPSE-509. --- Resolution: Fixed Fix Version/s: 2.6 Updating of the unavailable cache is now only done if downloading was true. > Unavailable cache is incorrectly updated to mark sources/javadoc as not > available when downloads option is not specified > > > Key: MECLIPSE-509 > URL: http://jira.codehaus.org/browse/MECLIPSE-509 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath) >Affects Versions: 2.5.1 >Reporter: Barrie Treloar >Assignee: Barrie Treloar > Fix For: 2.6 > > > If downloadSources is not specified and the source jar does not already exist > in the local repository then the unavailable cache was incorrectly updated to > indicate that the source for this artifact did not exist. Updating the > unavailable cache can only be done if the artifact was resolved against the > remote repositories (which requires downloadSources=true) > Similarly for downloadJavadocs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2300) Please upload EZMorph-1.0.6
Please upload EZMorph-1.0.6 --- Key: MAVENUPLOAD-2300 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2300 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 bug fixes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
