[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Edwin Punzalan closed MRM-42:
-
Resolution: Fixed
Patch applied. Thanks.
> discover repository metadata
>
>
> Key: MRM-42
> URL: http://jira.codehaus.org/
[ http://jira.codehaus.org/browse/MEV-265?page=comments#action_53698 ]
Matt Raible commented on MEV-265:
-
This same issue happens with commons-dbcp-1.2.1 and commons-pool-1.2.
Correcting the version number in each of these library's POMs fixes the
problem.
[ http://jira.codehaus.org/browse/MPARTIFACT-61?page=comments#action_53697
]
Joerg Schaible commented on MPARTIFACT-61:
--
@Arnaud: My key looks exactly the same and was generated with Cygwin's
ss-keygen. The file has Unix line endings though ...
@L
[ http://jira.codehaus.org/browse/MEV-140?page=comments#action_53696 ]
Matt Raible commented on MEV-140:
-
I'll send a message trying to get some Tapestry committers involved. One thing
that'd be nice if you changed immediately would be the version for
comm
[ http://jira.codehaus.org/browse/MNG-1848?page=all ]
Brett Porter closed MNG-1848:
-
Assign To: Brett Porter
Resolution: Duplicate
other issue describes problem
> Cannot execute "mvn clean" on plugins
> -
>
>
[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53694 ]
Brett Porter commented on MNG-661:
--
John - please create a new issue for your staging site problems
> In parent site, automatically create link to modules sites and vice-versa
>
[ http://jira.codehaus.org/browse/MNG-1834?page=all ]
Brett Porter closed MNG-1834:
-
Assign To: Brett Porter (was: John Casey)
Resolution: Won't Fix
Fix Version: (was: 2.0.2)
this is the result of using the wrong component expression. If
[ http://jira.codehaus.org/browse/MNG-1859?page=all ]
Brett Porter closed MNG-1859:
-
Resolution: Won't Fix
please comment on your use case for system scopes at: MNG-1867, see MNG-1471
for more information
> Allow all Dependeny Scopes to Optionally Ind
deprecate system scope, analyse other use cases
---
Key: MNG-1867
URL: http://jira.codehaus.org/browse/MNG-1867
Project: Maven 2
Type: Task
Components: design, Artifacts and Repositories
Reporter: Brett Porter
[ http://jira.codehaus.org/browse/MNG-1860?page=comments#action_53691 ]
Brett Porter commented on MNG-1860:
---
are we *certain* this worked in 2.0? I wouldn't think it should have.
> maven.* project references no longer resolve in ant tasks.
> --
[ http://jira.codehaus.org/browse/MNG-1456?page=all ]
Brett Porter closed MNG-1456:
-
Assign To: Brett Porter
Resolution: Won't Fix
> skipping tests faq
> --
>
> Key: MNG-1456
> URL: http://jira.codehaus.org/browse/
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53690 ]
Brett Porter commented on MNG-1857:
---
this is a design issue... do we need a reportingManagement element?
> PluginManagement config is not used by plugins enabled in the site generation
[ http://jira.codehaus.org/browse/MNG-1857?page=comments#action_53689 ]
Brett Porter commented on MNG-1857:
---
not really related to mng-1855
> PluginManagement config is not used by plugins enabled in the site generation
> phase
> -
[ http://jira.codehaus.org/browse/MNG-1864?page=all ]
Brett Porter closed MNG-1864:
-
Assign To: Brett Porter
Resolution: Duplicate
try using -U to get the updated javadoc plugin, I believe this has been
released.
> Menu links to javadoc uses wron
[ http://jira.codehaus.org/browse/MNG-1866?page=comments#action_53686 ]
Frank Mena commented on MNG-1866:
-
I forgot to mention that I attached the source.
> New SAR plugin
> --
>
> Key: MNG-1866
> URL: http://jira.codehaus.org/
New SAR plugin
--
Key: MNG-1866
URL: http://jira.codehaus.org/browse/MNG-1866
Project: Maven 2
Type: New Feature
Components: Plugin Requests
Versions: 2.0.1
Environment: plugin
Reporter: Frank Mena
Attachments: maven-sar-plugin.zip
I h
Ok, we only need to match up the sink, and by doing that in the api that
takes care of it. Everything is in the impl and selected by the
reporting plugin. If it upgrades to a new one, they need to change all
their references. I've tried this, and as long as the references are
updated correctly, it
Hi,
Can someone let me know about maven configurations with eclipse IDE.
Basically from eclipse , we need to plugin to maven which should do the
following
1) It should make a build.
2) It should deploy the application to the server.
3) It should run the test cases (cactus), which in turn shoul
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Maria Odea Ching updated MRM-42:
Attachment: MRM-42-repository-manager-discovery.patch
> discover repository metadata
>
>
> Key: MRM-42
> URL: http://jira.
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Maria Odea Ching updated MRM-42:
Attachment: (was: MRM-42-repository-manager-discovery.patch)
> discover repository metadata
>
>
> Key: MRM-42
> URL: h
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
updated MRM-42:
Attachment: MRM-42-repository-manager-discovery.patch
> discover repository metadata
>
>
> Key: MRM-42
> URL: http://jira.codehaus.org/browse/MRM-42
>
Commons Digester has invalid version number specified for xml-apis
--
Key: MEV-265
URL: http://jira.codehaus.org/browse/MEV-265
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Report
John Casey wrote:
> I was planning to release a RC version tonight, but if you think you
> can make improvements in this Doxia two-step we're putting together
> here, I think that is more important than a couple of days' time. I'll
> spend my time in more productive ways - namely, documenting the
>
[ http://jira.codehaus.org/browse/MEV-262?page=all ]
Edwin Punzalan closed MEV-262:
--
Assign To: Edwin Punzalan
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
> commons-email contains wrong dependencies
>
[ http://jira.codehaus.org/browse/MEV-261?page=all ]
Edwin Punzalan closed MEV-261:
--
Assign To: Edwin Punzalan
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
> acegi-security 0.8.2 depends on spring 1.2-
[ http://jira.codehaus.org/browse/MEV-264?page=comments#action_53669 ]
Dennis Lundberg commented on MEV-264:
-
The binary was previously removed from the repo as it was published by mistake.
So 1.1-dev should be removed from the metadata file.
> commons-
+1
Arnaud
On 12/18/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> +1
>
> On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > We've been receiving a lot of questions about the javadoc report, and
> > we've got some critical fixes ready for release which should solve a
> > go
commons-logging-1.1-dev is listed in maven-metadata, but no binary is found in
the repository
-
Key: MEV-264
URL: http://jira.codehaus.org/browse/MEV-264
Project: Maven Evangelism
commons-jexl POM missing 'commons-logging', although used in commons-jexl code
--
Key: MEV-263
URL: http://jira.codehaus.org/browse/MEV-263
Project: Maven Evangelism
Type: Bug
Components:
[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53654 ]
John Allen commented on MNG-661:
Additionall problem with new staging functionality and accessing uninterpolated
parent project attributes.
project.getParent() returns a project that has
Combined use of online and offline links
Key: MPJAVADOC-68
URL: http://jira.codehaus.org/browse/MPJAVADOC-68
Project: maven-javadoc-plugin
Type: Improvement
Versions: 1.7
Reporter: Wouter Hermeling
Priority: M
+1
On 12/14/05, John Casey <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We've been receiving a lot of questions about the javadoc report, and
> we've got some critical fixes ready for release which should solve a
> good deal of these problems. It looks like it's time to release the next
> beta of this p
[ http://jira.codehaus.org/browse/MNG-1834?page=comments#action_53651 ]
Olivier Lamy commented on MNG-1834:
---
I can't try because I have missing others dependencies :
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.reporting
ArtifactId: maven-
33 matches
Mail list logo
