Unable to download from Maven repository at ibiblio.org
---
Key: MAVEN-1737
URL: http://jira.codehaus.org/browse/MAVEN-1737
Project: Maven
Type: Bug
Components: core
Versions: 1.0.2
Environment: Gentoo
+1 for 2.0-beta-1
Emmanuel
Mike Perham a écrit :
All outstanding JIRA issues have been closed so I'd like to suggest a
new release.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
&sorter/order=ASC&sorter/field=priority&pid=11140&fixfor=12176
Brett asks:
- How does
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.073000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1783?page=comments#action_55377 ]
Dan Tran commented on MNG-1783:
---
should we move this to MRELEASE?
> maven-release-plugin doesn't pass username to maven-scm-provider-cvs
> -
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.071500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MDEPLOY-18?page=all ]
Brett Porter closed MDEPLOY-18:
---
Resolution: Won't Fix
> Problem with SCP deploy
> ---
>
> Key: MDEPLOY-18
> URL: http://jira.codehaus.org/browse/MDEPLOY-18
I keep on receiving spam from him by the way.
On 1/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> I'll do this... again.
>
> Jens Fournais wrote:
> > Best Regards
> > Global Identity A/S,
> >
> >
> > Jens Fournais
> > CEO
> >
> >
> > Bygstubben 3 | DK-2950 Vedbaek | Denmark
> > Phone: +45 45 99
[ http://jira.codehaus.org/browse/MDEPLOY-18?page=comments#action_55376 ]
Morten Kristiansen commented on MDEPLOY-18:
---
Yes. Giving the full path worked. Thanks.
> Problem with SCP deploy
> ---
>
> Key: MDEPLOY-18
>
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.07.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.064500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-282?page=comments#action_55374 ]
Edwin Punzalan commented on MEV-282:
is version 2.0-20040521 the public draft version?
> Please relocate jspapi:jsp-api to javax.servlet:jsp-api
>
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.063002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.06.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNGECLIPSE-11?page=all ]
Eugene Kuleshov closed MNGECLIPSE-11:
-
Resolution: Fixed
"Add dependency" menu enabled for pom.xml resources. Dependency will be added
into currently selected pom.xml
> adding depende
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.054501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.053000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNGECLIPSE-9?page=comments#action_55371 ]
Eugene Kuleshov commented on MNGECLIPSE-9:
--
In general this could be quite tricky. Eg. what if project has multiple poms?
> Classpath entries based on M2_REPO interfere with
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.051501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNGECLIPSE-14?page=all ]
Eugene Kuleshov updated MNGECLIPSE-14:
--
Priority: Minor (was: Major)
Lovering priority since reporter don't comment
> Maven enable menu not present on project
> ---
[ http://jira.codehaus.org/browse/MNGECLIPSE-24?page=all ]
Eugene Kuleshov closed MNGECLIPSE-24:
-
Resolution: Fixed
Added additional safeguards for long running/recursive tasks. Please try with
the next build and reopen issue if it still the sa
joda-time-1.2 has invalid pom
-
Key: MEV-283
URL: http://jira.codehaus.org/browse/MEV-283
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: david varnes
the pom deployed to ibiblio has the following snippet i
[ http://jira.codehaus.org/browse/MNGECLIPSE-7?page=all ]
Eugene Kuleshov closed MNGECLIPSE-7:
Resolution: Fixed
Local repository is automatically reindexed and index is also updated when
artifact are being downloaded.
> Search repository: Ver
[ http://jira.codehaus.org/browse/MNGECLIPSE-6?page=all ]
Eugene Kuleshov closed MNGECLIPSE-6:
Resolution: Fixed
Now search is using wildcards (like *log*)
> Search in repository fails for log4j
>
>
>
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.05.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=comments#action_55364 ]
Eugene Kuleshov commented on MNGECLIPSE-8:
--
I am not sure what is being suggested here. Red X would appear if Maven fail to
download selected artefact.
I am about to commit
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.044500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.043000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.041500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://svn.apache.org/repos/asf/maven/plugins/trunk
-D
On 1/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> The location of the Javadoc plugin listed here doesn't seem to be correct:
>
> http://maven.apache.org/plugins/maven-javadoc-plugin/source-repository.html
>
> $ svn checkout
> http://svn.
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060110.04.txt
The location of the Javadoc plugin listed here doesn't seem to be correct:
http://maven.apache.org/plugins/maven-javadoc-plugin/source-repository.html
$ svn checkout http://svn.apache.org/repos/asf/maven/components/trunk/maven-plu
gins/maven-javadoc-plugin maven-javadoc-plugin
svn: URL 'http://svn
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.034501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.031503.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
Brett Porter wrote:
+1 to 2.0-beta-1
Thanks again!
Mike Perham wrote:
All outstanding JIRA issues have been closed so I'd like to suggest a
new release.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
&sorter/order=ASC&sorter/field=priority&pid=11140&fixfor=12176
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.030001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.024501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.023000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.021502.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Mike Perham wrote:
I've fixed all outstanding issues with the PMD plugin. Who is allowed
to call for a release vote on it? PMC members?
+1
mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
[ http://jira.codehaus.org/browse/MAVENUPLOAD-644?page=all ]
Chris Sterling reopened MAVENUPLOAD-644:
It looks like the file was put into the wrong directory. Currently, they are in
the http://www.ibiblio.org/maven2/org/jini/maven-jini-plugin/
Brett Porter wrote:
They are deployed. I will have to check the instructions on the site
match up as it requires a normal repository rather than a plugin repository.
Any thoughts on this? should skins come from the plugin repository or
the project repository?
It's akin to an archetype being a
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.014500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.011501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-281?page=all ]
Edwin Punzalan closed MEV-281:
--
Assign To: Edwin Punzalan
Resolution: Fixed
Yes, you may create issues for these... but they will not be given priority.
This one has been fixed.
NOTE: May take
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060110.010001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.010001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
+1 to 2.0-beta-1
Thanks again!
Mike Perham wrote:
> All outstanding JIRA issues have been closed so I'd like to suggest a
> new release.
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
> &sorter/order=ASC&sorter/field=priority&pid=11140&fixfor=12176
>
>
> Brett ask
All outstanding JIRA issues have been closed so I'd like to suggest a
new release.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
&sorter/order=ASC&sorter/field=priority&pid=11140&fixfor=12176
Brett asks:
- How does its functionality compare to Maven 1.0?
Maven 1.x's
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060110.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
project-level plugin dependencies not handled correctly in multimodule builds
-
Key: MNG-1949
URL: http://jira.codehaus.org/browse/MNG-1949
Project: Maven 2
Type: Bug
Components: Plugins a
Thanks Mike, that's great! Really appreciated as I really didn't do much
more than experiment with it initially.
I have some questions first:
- How does its functionality compare to Maven 1.0?
- Is this a 2.0 release? Beta release?
If you want to answer those questions as part of a mail for the [
I've fixed all outstanding issues with the PMD plugin. Who is allowed
to call for a release vote on it? PMC members?
mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060110.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060110.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MCOMPILER-21?page=comments#action_55351 ]
Brian Fox commented on MCOMPILER-21:
2) if a parent version changes, rebuild everything
> compiler smarts
> ---
>
> Key: MCOMPILER-21
> URL: http:/
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=all ]
Leszek Gawron updated MRESOURCES-8:
---
Attachment: example.zip
> maven-resources-plugin ignores configuration/resources property
> ---
>
compiler parameters should be settable via properties for command line use
(patch attached)
---
Key: MCOMPILER-25
URL: http://jira.codehaus.org/browse/MCOMPILER-25
Project: Maven 2.x Com
[ http://jira.codehaus.org/browse/MPMD-4?page=all ]
mike perham closed MPMD-4:
--
Resolution: Fixed
Fix Version: 2.0-beta-1
Added Locator patch. Thanks Mark. Changed default rulesets to the same as
with the m1 plugin.
> PMD should use "sensible" def
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Brett Porter updated MRM-59:
Fix Version: 1.0-alpha-1
Component: remote proxy
> Proxy should work transparently with either maven 1.x or 2.x repositories.
> ---
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=all ]
Brett Porter reopened MRESOURCES-8:
---
ok, we should probably add a new mojo for copying files that will not be
packaged.
> maven-resources-plugin ignores configuration/resources property
> ---
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=comments#action_55342 ]
Leszek Gawron commented on MRESOURCES-8:
Brett unfortunatelly you don't. I need to use maven-resources-plugin in
generate-resources phase. I do not want src/main/properties a
Proxy should work transparently with either maven 1.x or 2.x repositories.
--
Key: MRM-59
URL: http://jira.codehaus.org/browse/MRM-59
Project: Maven Repository Manager
Type: New Feature
Repo
I'll do this... again.
Jens Fournais wrote:
> Best Regards
> Global Identity A/S,
>
>
> Jens Fournais
> CEO
>
>
> Bygstubben 3 | DK-2950 Vedbaek | Denmark
> Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED]
>
> Please visit our website at: http://www.elibitum.com
Best Regards
Global Identity A/S,
Jens Fournais
CEO
Bygstubben 3 | DK-2950 Vedbaek | Denmark
Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED]
Please visit our website at: http://www.elibitum.com
[ http://jira.codehaus.org/browse/MNGECLIPSE-26?page=comments#action_55332
]
Leonardo Quijano Vincenzi commented on MNGECLIPSE-26:
-
This is a global issue. It seems what I want can be done through External Tools
... Run ... JRE, so proba
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=all ]
Brett Porter closed MRESOURCES-8:
-
Assign To: Brett Porter
Resolution: Won't Fix
the configuration is not the place to do this.
If I understand correctly, you want to have filtered reso
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> They are deployed. I will have to check the instructions on the site
> match up as it requires a normal repository rather than a plugin
> repository.
>
> Any thoughts on this? should skins come from the plugin repository or
> the project reposi
I've adjusted .htaccess on ibiblio for /maven2 to set the correct width
for the filename column. Thanks to Fabrizio for the tip!
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
[ http://jira.codehaus.org/browse/SUREFIRE-7?page=all ]
Jason van Zyl updated SUREFIRE-7:
-
Fix Version: 1.5.3
> Targets for unit, integration and functional tests
> --
>
> Key: SUREFIRE-7
>
[ http://jira.codehaus.org/browse/SUREFIRE-23?page=all ]
Jason van Zyl updated SUREFIRE-23:
--
Fix Version: 1.5.3
> Output of tests in forked mode to file instead to System.out
>
>
> Ke
[ http://jira.codehaus.org/browse/SUREFIRE-21?page=all ]
Jason van Zyl updated SUREFIRE-21:
--
Fix Version: 1.5.3
> Use plexus-utils and get rid of the copied util files
> --
>
> Key: SUREFIRE-
They are deployed. I will have to check the instructions on the site
match up as it requires a normal repository rather than a plugin repository.
Any thoughts on this? should skins come from the plugin repository or
the project repository?
- Brett
Carlos Sanchez wrote:
> what about deploying the
what about deploying the snapshots?
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> If they are using development snapshots they need to use them properly.
> The skins will be released when the site plugin is and its tested, so we
> are sure that they are final.
>
> - Brett
>
> Vincent Siveto
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060109.214501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060109.214501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MPLUGIN-7?page=comments#action_55325 ]
Hervé BOUTEMY commented on MPLUGIN-7:
-
Hi Vincent,
Sorry, I did not explain myself clearly : I'm new to Maven2 internals (which
are huge, but great)...
What I'm trying to do is to
Heh, that's interesting. I'll put a rule in for that one specifically.
Another issue just discovered: we let all kinds of crap to sync into the
m1 repo, including development builds. We don't convert them to the
maven 2.x repo. That now breaks builds that depended on the snapshots.
Do we:
a) do a
reporting section should allow additional dependencies in plugins as well
-
Key: MNG-1948
URL: http://jira.codehaus.org/browse/MNG-1948
Project: Maven 2
Type: Improvement
Components: POM, Plug
I believe that's caused by the rewrite rules, they don't work well
with dirs but they do with artifacts
On 1/9/06, Felipe Leme <[EMAIL PROTECTED]> wrote:
> Weird, it was screwed a couple of minutes ago (the
> http://www.ibiblio.org/maven was redirecting to the
> http://www.ibiblio.org/maven/public
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060109.213001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060109.213001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060109.213000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060109.213000.txt
[ http://jira.codehaus.org/browse/MNGECLIPSE-26?page=comments#action_55324
]
Eugene Kuleshov commented on MNGECLIPSE-26:
---
Can you please provide simple project to make it easier to reproduce this
issue. Thanks.
> Allow to specify a custom JDK for
[ http://jira.codehaus.org/browse/DOXIA-43?page=all ]
Brett Porter moved MNG-1947 to DOXIA-43:
Version: (was: 2.0.1)
Component: (was: Plugins and Lifecycle)
Complexity: (was: Intermediate)
Workflow: jira (was: Maven)
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060109.21.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060109.21.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060109.21.txt
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=comments#action_55319 ]
Leszek Gawron commented on MRESOURCES-8:
Thank you. It works like a charm. Will this patch get eventually into official
sources?
> maven-resources-plugin ignores configurati
Yes, both proxy and firewall.
But no problem for Maven 2 itself.
I am not sure, which bugs are Major compared to Minor, but that is up to
what
level of maturity the plug-in is supposed to reach over time ;-)
-Original Message-
From: Eugene Kuleshov (JIRA) [mailto:[EMAIL PROTECTED]
Sent:
Mike Perham wrote:
> I updated the PMD plugin to use plugin-parent 2.0.1 instead of 2.0 and
> it started generating the documentation. Does this force the use of
> maven 2.0.1? I believe so because plugin-parent 2.0.1 pulls in
> maven-project 2.0.1.
It will still use the installed maven-project.
I didn't know that. Well anyway, current solution works for me and as
I said, I will fully test it torrow in an integration scenario.
s/
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Stephane Nicoll wrote:
> > Hi,
> >
> > I have implemented the integration for the eclipse plugin. It does
If they are using development snapshots they need to use them properly.
The skins will be released when the site plugin is and its tested, so we
are sure that they are final.
- Brett
Vincent Siveton wrote:
> Hi,
>
> Could we release the maven skins? It's failing the execution when people try
> t
What do you mean by "snapshot version for the sources"?
- Brett
Scokart Gilles wrote:
>
>
> I notice that there is no snapshots version for the sources on the 2.0.x
> versions. Is it correct? Is it possible to have it? (And would it be
> useful?)
>
>
>
> Thanks,
>
>
>
> SCOKART Gille
Stephane Nicoll wrote:
> Hi,
>
> I have implemented the integration for the eclipse plugin. It does not
> use wagon in the aim to be compatible with maven 1.0.x.
>
I don't understand this. You can still use wagon (as an average plugin
dependency) in Maven 1.0.x.
- Brett
---
[ http://jira.codehaus.org/browse/MNGECLIPSE-29?page=all ]
Eugene Kuleshov updated MNGECLIPSE-29:
--
Priority: Minor (was: Major)
Please provide sample project to make it easier to reproduce this issue.
Do I understand correctly that you are behind
[ http://jira.codehaus.org/browse/MNG-1927?page=comments#action_55316 ]
Brett Porter commented on MNG-1927:
---
its been noted that this isn't always the case, depending on environment. This
leads me to believe it could be related to the introduction of envir
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060109.21.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060109.21.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Plug-In does not run behind Proxy/Firewall (where M2 itself does)
-
Key: MNGECLIPSE-29
URL: http://jira.codehaus.org/browse/MNGECLIPSE-29
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
Environment: W
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060109.194500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060109.194500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNG-1941?page=all ]
Jason van Zyl updated MNG-1941:
---
Fix Version: (was: 2.0.2)
> add an introduction to plugin configuration (patch included)
>
>
>
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=all ]
Chris Hagmann updated MRESOURCES-8:
---
Attachment: MRESOURCES-8-workaround.patch
> maven-resources-plugin ignores configuration/resources property
> ---
Hi,
I have implemented the integration for the eclipse plugin. It does not
use wagon in the aim to be compatible with maven 1.0.x.
The patch is attached to the MPECLIPSE-60 issue
(http://jira.codehaus.org/secure/attachment/18498/MPECLIPSE-60.patch)
Can someone please review it? I will fully test
[ http://jira.codehaus.org/browse/MPECLIPSE-60?page=all ]
Stephane Nicoll updated MPECLIPSE-60:
-
Attachment: MPECLIPSE-60.patch
> Downloading source zips
> ---
>
> Key: MPECLIPSE-60
> URL: http://jira.codehaus.or
I updated the PMD plugin to use plugin-parent 2.0.1 instead of 2.0 and
it started generating the documentation. Does this force the use of
maven 2.0.1? I believe so because plugin-parent 2.0.1 pulls in
maven-project 2.0.1.
Is it better to just list the plugin report in PMD's POM instead? As a
u
[ http://jira.codehaus.org/browse/MNGECLIPSE-28?page=all ]
Eugene Kuleshov updated MNGECLIPSE-28:
--
Priority: Minor (was: Critical)
Please make sure that you haven't specified any path to m2 repository in plugin
properties. If it still won't work,
1 - 100 of 153 matches
Mail list logo
