TLDR; issue fixed :)
tracked in https://issues.apache.org/jira/browse/MSITE-863
fixed in maven-reporting-exec 1.5-SNAPSHOT
https://issues.apache.org/jira/browse/MSHARED-921
this is caused by Xpp3Dom class incompatibility with
Xpp3DomUtils.mergeXpp3Dom(...):
- Xpp3Dom version is taken from Mave
On Mon, May 25, 2020 at 2:49 AM Hervé BOUTEMY wrote:
>
> removing Maven 2 code is a good simplification
> but FYI it won't remove dependency on plexus-classworld: it's the core of all
> plugins classloading mechanism to have independant plugins
>
Yes, but there's an explicit dependency on classor
Hi Hervé,
you can reproduce the issue on mojohaus parent repository
(github.com:mojohaus/mojo-parent.git) and using the branch "issue-105"
and just:
mvn site site:stage
Using Maven 3.5.2 fails with the described issue.
Kind regards
Karl Heinz Marbaise
On 25.05.20 08:41, Hervé BOUTEMY wrote:
removing Maven 2 code is a good simplification
but FYI it won't remove dependency on plexus-classworld: it's the core of all
plugins classloading mechanism to have independant plugins
didn't yet have time yet to dig, but perhaps the way maven-site-plugin invokes
reporting plugins causes some dep
uh, strange: maven-site-plugin ITs are ok with many Maven and JDK versions [1]
I'll need some time to investigate
Regards,
Hervé
[1]
https://builds.apache.org/blue/organizations/jenkins/maven-box%2Fmaven-site-plugin/detail/master/94/pipeline
Le dimanche 24 mai 2020, 12:01:46 CEST Karl Heinz
I still don't have full grasp of the cause, but I think we can remove
our dependency on plexus-classworlds completely by ripping out some
Maven 2 support. See
https://github.com/apache/maven-site-plugin/pull/24/f
On Sun, May 24, 2020 at 6:16 AM Elliotte Rusty Harold
wrote:
>
> getInputLocation
getInputLocation seems to have been added in plexus-utils 3.2.0.
The reproducible builds work for maven-site-plugin upgraded from
plexus 3.0.x to 3.3.0 in
https://github.com/apache/maven-site-plugin/commit/19be00a9bf2a410abb7132487dc24055060b2c70#diff-600376dffeb79835ede4a0b285078036
It's not imm
For clarity, I was testing against 3.3.9. I tried with 3.5.4 today without
a change in results. However, I did discover something interesting that I
confirmed in both versions...
Given my setup:
*) Utility jar has several plexus components and non-components
*) Utility jar has an AbstractMavenLife
MNG-6209 is indeed the first issue that comes to my mind and I wonder if
this is fixed. I thought it was reverted after issues with the 3.5.1
release.
Together with Stephen we've tried to define how this should work.
He wrote some tests[1] to demonstrate the issue.
I've tried to show the diff
>>From "Failed to create parent directories"...
It is multi-module project but it does not have any parent POM. It is fully
isolated project - Microservice.
>>Local repo directory ownership/permissions?
All is done in my user home.
cd ~
git clone ...
cd ...
mvn -X -U clean
Thx
Tibor
On Tue, N
My 5c:
>From "Failed to create parent directories"...
Local repo directory ownership/permissions?
HTH,
T
On Tue, Nov 28, 2017 at 7:21 PM Tibor Digana wrote:
> The settings.xml:
>
>
> http://maven.apache.org/SETTINGS/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
The settings.xml:
http://maven.apache.org/SETTINGS/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
/home/xms40/.m2/repository
These are my logs from mvn -X clean
[DEBUG] Using mirror nexus (
http://mavenrepo.ads.local/nexus/content/groups/public) for central (
https://repo.maven.apache.org/maven2).
...
[DEBUG] Using transporter WagonTransporter with priority -1.0 for
http://mavenrepo.ads.local/nexus/content/groups/public
I tried to use Proxy in settings.xml and nonProxyHosts separated by pipe |
with same result, but this is not necessary to do since our company is
using Nexus.
The funny thing is that I wrote Java code which downloads Arquillian from
the same URL.
The Jenkins also works almost well (with host name o
Did you also configure your proxy in the settings.xml? [1]
Hth,
Nick
[1] https://maven.apache.org/guides/mini/guide-proxies.html
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have
I guess we need to dive into MethodHandles.Lookup[1] or reconsider
MultiRelease JAR
[1]
http://download.java.net/java/jigsaw/docs/api/java/lang/invoke/MethodHandles.Lookup.html
On Sat, 06 May 2017 09:24:51 +0200, Tibor Digana
wrote:
Hi,
@Robert I created branch [1] and added Java 9 m
Hi Tibor,
(If it helps) I guess detecting you run on java 9 you can add some
--add-opens on the CLI as a workaround. Otherwise a double compilation can
be needed or just provide a jar with these classes in the classloader which
will override the JVM ones - this is how it should work for the deprec
Yesterday I talked with INFRA team and it was fixed. I was looking for the
email around 15 Nov and it was 25 Nov.
Anyway thx for help. I am ssh to minotaur.apache.org.
On Thu, Aug 11, 2016 at 5:48 AM, Olivier Lamy [via Maven] <
ml-node+s40175n5877590...@n5.nabble.com> wrote:
> Hey
> people.apache
Hey
people.apache.org is now home.apache.org
You should have received an email for that?
Cheers
Olivier
On 11 August 2016 at 05:57, Tibor Digana wrote:
> I can connect to peo...@apache.org via WinSCP. First time it asked me to
> update the certificate and I am in, but I cannot login via PuTTY.
I never suggested that it should hinder the release. I was able to
test it myself, it's my co-worker who couldn't join in. You do have a
+1 from me, I look forward to the announcement.
On Sun, Oct 18, 2015 at 8:18 AM, Michael Osipov wrote:
> Am 2015-10-16 um 15:01 schrieb Benson Margulies:
>>
>>
Am 2015-10-16 um 15:01 schrieb Benson Margulies:
Maven-plugins 28 is released, of course; what's up? It worked for me,
but not for one of my co-workers.
Benson,
where you actually able to resolve your problem? From my point of view
this should not hinder the plugin release.
Michael
--
On Fri, Oct 16, 2015 at 9:38 AM, Anders Hammar wrote:
> No, you don't. Maybe there is some cached metadata incorrect or the
> metadata at apache.
> Could you try adding the -U switch?
>
> Also, I only have the staging repo in my settings as a profile and I only
> activate it explicitly when testin
No, you don't. Maybe there is some cached metadata incorrect or the
metadata at apache.
Could you try adding the -U switch?
Also, I only have the staging repo in my settings as a profile and I only
activate it explicitly when testing staged stuff.
/Anders (mobile)
Den 16 okt 2015 15:35 skrev "Ben
Anders, I added a pluginRepository for the stage to my settings.xml.
As far as I know, adds, it
doesn't replace.
So why isn't it searching for the parent in the usual way in the other
repositories? Or do I have to manually put central in as a
pluginRepository if I'm just trying to add one?
It looks like a specific staging repo is accessed (look at the URL in the
end). As the parent has been released it is no longer available there.
/Anders (mobile)
Den 16 okt 2015 15:01 skrev "Benson Margulies" :
> Maven-plugins 28 is released, of course; what's up? It worked for me,
> but not for
Hi,
After diving more into this:
The line in NPE given 736 in AbstractZipArchiver (plexus-archiver:3.0.1):
// Close the output stream.
try
{
if ( zipArchiveOutputStream != null )
{
zOut.writeTo( zipArchiveOutputStream ); <-- 736
Hi Robert,
yes it works before i made the changes...
and just for the record i undone the changes and retested and it worked
as expected without the changes...
Kind regards
Karl Heinz Marbaise
On 9/29/15 9:58 PM, Robert Scholte wrote:
Hi Karl Heinz,
Just to be sure: did it work on your sys
Hi Karl Heinz,
Just to be sure: did it work on your system before you made these changes?
Robert
Op Tue, 29 Sep 2015 20:31:03 +0200 schreef Karl Heinz Marbaise
:
Hi,
I'm trying to upgrade shared maven-archiver to 3.0 minimumetc.
dependencies etc. (Branch:
https://svn.apache.org/rep
Well, at the moment it's the Android SDK team, but in the future it could
be anybody.
I look at the deployed POMs are as form of contract between the deployed
artifact and it's consumers. So when the contract isn't explicit (eg
dependency type info) then its open to misinterpretation.
Maven conve
On Jan 20, 2015, at 6:03 PM, William Ferguson
wrote:
> Been thinking about this a little more.
>
> The TLDR version: I am suggesting that we provide more information and
> place a stricter syntax requirement of the POM *generated* by the build.
> This allows the generated POM to be a clear con
Been thinking about this a little more.
The TLDR version: I am suggesting that we provide more information and
place a stricter syntax requirement of the POM *generated* by the build.
This allows the generated POM to be a clear contract between the deployed
artifact and it's consumers, regardless
Yes I supposed last few commits won't be able undo other way. Next time this
will not happen, we will make "safe" commitments first.
What branches were introduced?
The apache branch had master and surefire-954-test only.
The whole problem was with maven-release-plugin:2.2.1 and some other with
SS
I see you have pushed some "interesting" committs to surefire master @
apache. These are a permanent part of history, and cannot be undone.
You also pushed a few "interesting" branches, which I took the liberty
of deleting, sicne they were pointing to existing history.
In general, I find that usin
When you do the git reset --hard command you basically move your local
"master" branch back somewhere else in history. If you make a commit
at the point, you will not be able to push to apache, since it refuses
to rollback history.
To get out of this situation you need to do git merge origin/maste
It's not the repository layout that Google is not honouring. It's the
semantics of the unspecified dependency type in the POMs in that repository.
If the POM syntax were changed to require that deps had a type then Maven
itself could fail the build because it could determine that the inputs were
in
On 2014-12-19, 17:40, William Ferguson wrote:
I'd love to go the first route, but unfortunately Google is only making the
Android libraries available via a repository that is downloaded (and
updated) via the Android SDK. So they are not visible on Maven Central and
Maven Central obviously couldn'
I'd love to go the first route, but unfortunately Google is only making the
Android libraries available via a repository that is downloaded (and
updated) via the Android SDK. So they are not visible on Maven Central and
Maven Central obviously couldn't vet them.
The second option would work, but I
Ok, I understand the problem now, but I don't think forcing everything
to explicitly state dependency type is the right solution here.
"Convention over configuration" is one of fundamental Maven principals,
and by convention dependencies are assumed to have type=jar.
I see two possible ways to im
4306.html"http://www.wrox.com/
>
> Kindle Version: HYPERLINK
> "http://www.amazon.com/Professional-Oracle-WebLogic-Server-ebook/dp/B004HD69J2/"http://www.amazon.com/
>
>
>
>
>
> From: William Ferguson [mailto:william.fergu...@xandar.com.au]
> Sent: S
Sorry Igor, I see now I omitted a chunk of context.
The reason for the error is that this component :
com.android.support
support-v13
21.0.2
aar
has a dependency upon
com.android.support
support-v4
21.0.2
William Ferguson [mailto:william.fergu...@xandar.com.au]
Sent: Sunday, December 07, 2014 6:25 PM
To: maven-android-develop...@googlegroups.com
Cc: Maven Developers List
Subject: Re: problem with AAR dependency
## Cross posting to Maven Dev list
One solution to this would be to change the
I am not sure I follow. Can you explain what actually happens and how
forcing element for all projects dependencies is expected to help
the problem?
--
Regards,
Igor
On 2014-12-07, 19:25, William Ferguson wrote:
## Cross posting to Maven Dev list
One solution to this would be to change the PO
## Cross posting to Maven Dev list
One solution to this would be to change the POM specification to require
the type element for dependencies.
That would allow Maven and MavenCentral to immediately fail POMs based upon
dependencies that are missing the type element.
Yes, it goes against convent
Thank You @Stuart McCulloch (and others that helped me in this topic)! Your
explanation is very valuable and resolved my problems :)
Regards,
animator.
--
View this message in context:
http://maven.40175.n5.nabble.com/Problem-while-getting-injected-parameters-from-plugin-configuration-tp580589
On 22 Sep 2014, at 23:34, animator wrote:
> The main problem from the topic finally I managed to resolve. The problem was
> wrong configuration in test-polyglot-project, the groupId of declared plugin
> in pom was wrong and when the goal was executed it was used plugin from
> local repository and
You need to use org.apache.maven.plugins.annotations.Component
annotation inside maven plugins, I don't believe plexus @Requirement
works.
--
Regards,
Igor
On 2014-09-22, 18:34, animator wrote:
The main problem from the topic finally I managed to resolve. The problem was
wrong configuration in
The main problem from the topic finally I managed to resolve. The problem was
wrong configuration in test-polyglot-project, the groupId of declared plugin
in pom was wrong and when the goal was executed it was used plugin from
local repository and any configuration from pom was omitted.. Anyway tha
On 21 Sep 2014, at 22:54, animator wrote:
> Thanks for answers!
>
> I removed reporting section and unfortunately it doesn't work.. (*1)(btw.
> before that I added reporting api and declared InstrumentMojo extends
> AbstractMavenReport but this doesn't work too).
>
> I suppose may be there is
Thanks for answers!
I removed reporting section and unfortunately it doesn't work.. (*1)(btw.
before that I added reporting api and declared InstrumentMojo extends
AbstractMavenReport but this doesn't work too).
I suppose may be there is problem with plexus, because when I added
Component annot
no, there is absolutely nothing related to reporting plugins: reporting
plugins are exactly like plugins
I didn't see test-polyglot-project, I just had a reaction when looking at the
mojo source
when I look at test-polyglot-project, I see another problem: why is it
reclared in reporting secti
On 2014-09-21, 12:14, Hervé BOUTEMY wrote:
hte attribute "without property" seems to be expected to be a Plexus
component, but you didn't declare it:
Is this specific to reporting plugins? I believe regular plugins
can have @Parameter's without properties and/or default values.
--
Regards,
Igo
hte attribute "without property" seems to be expected to be a Plexus
component, but you didn't declare it:
1. in ClojureExecutorImpl, you should use Plexus @Component annotation like
http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/xref/org/apache/maven/plugin/checkstyle/e
Yes, of course,
plugin: https://github.com/lgadawski/cloverage-maven-plugin ,
test project: https://github.com/lgadawski/test-polyglot-project
Mojo class:
https://github.com/lgadawski/cloverage-maven-plugin/blob/master/src/main/java/com/gadawski/maven/plugins/cloverage/goals/InstrumentMojo.java
Hi,
can you please show the full pom file of your plugin project ?
Is this project somewhere available on Github or so ? So we can take a
look at it...
Kind regards
Karl-Heinz Marbaise
On 9/21/14 12:28 PM, animator wrote:
Hi,
I'm developing custom reporting plugin for my own needs. I use
> This problem is specific to maven-plugin-testing-harness. You can use
> any version of Guava at runtime, but test classpath is flat so you need
> to use single Guava version that is compatible with all components.
>
> Unfortunately, I don't know how to fix the problem, at least not until
> Maven
On 24 Jan 2014, at 23:49, Igor Fedorenko wrote:
> This problem is specific to maven-plugin-testing-harness. You can use
> any version of Guava at runtime, but test classpath is flat so you need
> to use single Guava version that is compatible with all components.
>
> Unfortunately, I don't know
This problem is specific to maven-plugin-testing-harness. You can use
any version of Guava at runtime, but test classpath is flat so you need
to use single Guava version that is compatible with all components.
Unfortunately, I don't know how to fix the problem, at least not until
Maven core is us
Hi,
Please use the Maven Users list instead. This list is meant for actual
development of Maven itself.
Vincent
2013/9/22 Suranga Kasthurirathne
> Hi,
>
> I apologize in advance if this email contains sketchy / incomplete details.
> I'm not really a maven expert, and would love any advice tha
Thank you for the responce , I'll try 2.1.0 until the release of 2.1.2 on 30
september :) it's soon
Date: Tue, 27 Sep 2011 08:51:35 -0700
From: ml-node+s40175n4845847...@n5.nabble.com
To: amy...@live.fr
Subject: Re: problem to build maven 3 project from hudson console
On 2
On 27 Sep 2011, at 14:39, Amiragl wrote:
> Hi community,
>
> I'm using : apache-maven-3.0.3 , hudson-2.1.1 but i'm having this error
> during building my project
Looks like http://issues.hudson-ci.org/browse/HUDSON-9004
This will be fixed in 2.1.2 (expected soon) otherwise you could try the Ma
Hi,
Please post on the users list.
This one is for developing Maven core.
Cheers
Le 5 août 2011 22:14, "Oskar S" a écrit :
> Hello,
>
> We're using the PMD plugin to run both PMD and CPD on our codebase,
however,
> we've come across
> a problem that has led us to disable CPD as a workaround. Spe
Using help:effective-pom it shows the 'correct', in term of Maven 3,
scope which is not the expected scope.
Whatever scope I set in my pom it is the scope defined (or not) in the
parent pom's dependency management that is used.
this is quite blocking as it means that you can't use the
dependecyMana
Emmanuel Hugonnet wrote:
How can I display the genuine scope of my dependecy ?
mvn -X ...
The debug log will print the project dependency tree before the project
gets build.
Benjamin
-
To unsubscribe, e-mail: dev-unsubsc
Hello,
What is the output of the cli : /bin/sh -c cd
/home/samuel/workspace/DQAWorkspace/CMTB && cvs -z3 -f -d
:pserver:samuel@192.168.1.8:/bosco/cvsrep -n -q rls -d -e -R DQA/Doc
?
2011/2/16 samuellawrence :
>
> Dear All,
>
> I am working on maven-scm-client using api. When I use list cvs comma
> Internal error in the plugin manager executing goal
> 'org.apache.axis2:axis2-wsdl2code-maven-plugin:1.4.1:wsdl2code': Unable to
> find the mojo
> 'org.apache.axis2:axis2-wsdl2code-maven-plugin:1.4.1:wsdl2code' in the
Sounds like an issue in the plugin. I'd report it to the Axis2 team
and see wh
Hi Jason,
I hit the same issue. I hope you raised a JIRA!
Since I'm impatient and can't wait for a resolution, I'm planning on getting
around it by renaming directories and module names in my root pom via an ant
task bound to the process-sources phase of my archetype build.
Here's hoping it w
Hi Jason,
Your need is not currently taken in the archetype plugin which assumes
that sub-modules are refered in in the parent.
Please raise a Jira.
Raphaël
2009/4/8 Jason Voegele :
> Hello again maven-archetype gurus.
>
> I am working on an archetype where the generated project should have the
If you jar up your plugin project I'll take a look. Create a JIRA
issue and attach the project and I'll see it.
On 16-Dec-08, at 6:34 PM, Alfie Kirkpatrick wrote:
Hi, I am attempting to write a plugin that uses Velocity to template
some config files. I have been developing the plugin using m2
Niall Pemberton wrote:
On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]>
wrote:
What does -X tell you?
Not alot that makes any sense to me, but thanks for the suggestion - I
ran i
iall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 29, 2008 11:08 AM
> To: Maven Developers List
> Subject: Re: Problem finding loadresource task in maven 2.0.9
>
> On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]>
> wrote:
>> Niall Pe
want to fix it for .10.
-Original Message-
From: Niall Pemberton [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 29, 2008 11:08 AM
To: Maven Developers List
Subject: Re: Problem finding loadresource task in maven 2.0.9
On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTE
On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Niall Pemberton wrote:
>>
>> On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> What does -X tell you?
>>
>> Not alot that makes any sense to me, but thanks for the suggestion - I
>> ran it
Niall Pemberton wrote:
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
What does -X tell you?
Not alot that makes any sense to me, but thanks for the suggestion - I
ran it with that option for both maven 2.0.8 and 2.0.9 and the output
for both is here:
http://people.ap
On Sun, Jun 29, 2008 at 5:20 AM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> This caught my eye. I have no idea what it means though or if it could be
> responsible for the problem.
>
> The following artifacts were filtered out for plugin:
> org.apache.commons:commons-build-plugin:1.0 because they're
This caught my eye. I have no idea what it means though or if it could
be responsible for the problem.
The following artifacts were filtered out for plugin:
org.apache.commons:commons-build-plugin:1.0 because they're already in the core
of Maven:
Niall Pemberton wrote:
On Sat, Jun 28, 2008
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> What does -X tell you?
Not alot that makes any sense to me, but thanks for the suggestion - I
ran it with that option for both maven 2.0.8 and 2.0.9 and the output
for both is here:
http://people.apache.org/~niallp/commons-
What does -X tell you?
Niall Pemberton wrote:
Anyone got any ideas on this - should I open a JIRA ticket (if so
against what?) or should I have asked this on the user list? I posted
here coz it looks like a maven bug to me.
Niall
On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton
<[EMAIL PROTECT
Anyone got any ideas on this - should I open a JIRA ticket (if so
against what?) or should I have asked this on the user list? I posted
here coz it looks like a maven bug to me.
Niall
On Fri, May 16, 2008 at 3:02 PM, Niall Pemberton
<[EMAIL PROTECTED]> wrote:
> I recently upgraded from maven 2.0.
On Fri, Jun 27, 2008 at 10:35 AM, Hoeher, Alexander <
[EMAIL PROTECTED]> wrote:
> Hello Maven people,
>
> I have the current version of Maven, Maven 2.0.9 installed.
> Any helpful comments welcome!
>
> A. Problem
> This is the problem, abstract:
> How can I disambiguate jar names of jars taken fro
Try having a look at this example:
https://svn.codehaus.org/mojo/trunk/sandbox/fit-maven-plugin/src/main/java/org/codehaus/mojo/fit/
Cheers
Claudio Ranieri wrote:
Hi
I am trying to create a maven plugin to jboss wsconsume, but I have a problem
with classloader in plugin.
My plugin is based i
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
After an epiphany, I found the problem: A corrupt JAR file in the
repository. I've opened http://jira.codehaus.org/browse/MNG-3523
The bug is still there in 2.0.9. I've downloaded the source and the bug
lurks in this code:
MavenPluginCollector.java
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
The bug is still there in 2.0.9. I've downloaded the source and the bug
lurks in this code:
MavenPluginCollector.java:
public PluginDescriptor getPluginDescriptor( Plugin plugin )
{
// TODO:
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
The bug is still there in 2.0.9. I've downloaded the source and the
bug lurks in this code:
MavenPluginCollector.java:
public PluginDescriptor getPluginDescriptor( Plugin plugin )
{
// TODO: include version, but can't do this in the
Aaron Digulla schrieb:
> Brian E. Fox schrieb:
>
>> I think it's safer to leave it at beta-6. Most people aren't expressing any
>> issues and if anyone has trouble, they can manually lock to beta-5. This is
>> safer than potentially downgrading everyone.
>
> beta-6 doesn't work for me at all. I
Brian E. Fox schrieb:
> I think it's safer to leave it at beta-6. Most people aren't expressing any
> issues and if anyone has trouble, they can manually lock to beta-5. This is
> safer than potentially downgrading everyone.
beta-6 doesn't work for me at all. I suddenly get:
java.lang.IllegalS
lock to beta-5. This is safer than potentially downgrading everyone.
-Original Message-
From: Bouiaw [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008 11:51 AM
To: Maven Developers List
Subject: Re: problem with site-plugin 2.0-beta-6
Hi,
Just an information that is important
l 02, 2008 11:51 AM
To: Maven Developers List
Subject: Re: problem with site-plugin 2.0-beta-6
Hi,
Just an information that is important (from my point of view) to know.
Site plugin beta-6 has an important issue (
http://jira.codehaus.org/browse/MSITE-270) : with multi modules projects,
menus
t; but that may potentially downgrade some users.
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2008 4:34 AM
> To: Maven Developers List
> Subject: Re: problem with site-plugin 2.0-beta-6
>
> I've had problems with b
:34 AM
To: Maven Developers List
Subject: Re: problem with site-plugin 2.0-beta-6
I've had problems with beta-6 too - I wonder if we should stick with
beta-5 in 2.0.9?
I'm unsure why 2.0.8 was using beta-5 while 2.0.9 uses beta-6, as
David said that it was not specified in his P
On Wed, Apr 2, 2008 at 10:18 AM, <[EMAIL PROTECTED]> wrote:
>
> Ran 209rc6 and as a side effect the site-plugin version got resolved to
> 2.0-beta-6 which gave me the following problem:
...
>
> [INFO] [site:attach-descriptor]
> [DEBUG] Mapped url: /tmp/dnbnorapi-trunk/src/site to relative path:
I've had problems with beta-6 too - I wonder if we should stick with
beta-5 in 2.0.9?
I'm unsure why 2.0.8 was using beta-5 while 2.0.9 uses beta-6, as
David said that it was not specified in his POMs on IRC.
Cheers,
Brett
On 02/04/2008, at 7:18 PM, [EMAIL PROTECTED] wrote:
Ran 209rc6 a
dnesday, March 19, 2008 8:08 PM
> To: Maven Developers List
>
> Subject: Re: problem with plugin-plugin 2.4
>
> Hi Brian,
>
> Mmmh. I didn't expect this problem with maven 2.0.8 or below but with
> 2.0.9.
> Due to changes made in 2.0.9, the plugin now needs do
I don't follow. What changes?
-Original Message-
From: Vincent Siveton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 8:08 PM
To: Maven Developers List
Subject: Re: problem with plugin-plugin 2.4
Hi Brian,
Mmmh. I didn't expect this problem with maven 2.0.8 or belo
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> This also seems related to the latest release. Looks like we're going to
> need to respin this stuff pretty quickly:
> http://jira.codehaus.org/browse/MPLUGIN-102
>
I don't think it is related, I will comment.
Cheers,
Vincent
> -Original Mes
Hi Brian,
Mmmh. I didn't expect this problem with maven 2.0.8 or below but with 2.0.9.
Due to changes made in 2.0.9, the plugin now needs doxia-core with
runtime scope (???).
Cheers,
Vincent
2008/3/19, Brian E. Fox <[EMAIL PROTECTED]>:
> Today I'm not able to build the maven-dependency-plugin s
This also seems related to the latest release. Looks like we're going to
need to respin this stuff pretty quickly:
http://jira.codehaus.org/browse/MPLUGIN-102
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 5:52 PM
To: Maven Developers List
Also, you should not post these types of questions to Dev. Instead,
post to the Users list
Wayne
On 12/12/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> What do you mean, you're using an "old Maven central"? Did you
> download the entire Central repo?
>
> You can always just manually create the file
What do you mean, you're using an "old Maven central"? Did you
download the entire Central repo?
You can always just manually create the file structure etc. The
archetypes are simply available to make things easier for you to get
stuff set up.
Wayne
On 12/12/07, Jens Rapp <[EMAIL PROTECTED]> wro
You should not be sending these emails to Maven Dev list. This has
nothing to do with the development of Maven software.
Instead you should be sending these emails to the Maven Users list:
[EMAIL PROTECTED]
See more info: http://maven.apache.org/mail-lists.html
Wayne
On 9/4/07, Hemant Ved <[EMA
was6.0
On 9/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> Which version of WebSphere is this?
>
> Hermod
>
> -Original Message-
> From: Hemant Ved [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 04, 2007 11:07 AM
> To: dev@maven.apache.org
> Cc: [EMAIL PROTECTED]
> Sub
1 - 100 of 205 matches
Mail list logo
