Thanks for the blazing-fast help, Olivier.
Regarding the Java 5 language updates I referred to in my original post, I
created http://jira.codehaus.org/browse/MINVOKER-114 MINVOKER-114 .
--
View this message in context:
http://maven.40175.n5.nabble.com/feedback-on-maven-invoker-plugin-patches-t
Hi,
I created two issues for maven-invoker-plugin:
"duplicate script classpath entries are not filtered out, can cause
ClassCastException" - http://jira.codehaus.org/browse/MINVOKER-112
and
"update to Groovy 1.7.5 (from 1.5.6)" -
http://jira.codehaus.org/browse/MINVOKER-113
The first issue i
Hervé BOUTEMY wrote:
>
> seems like this will be the big addition in 2.1
> and your summary is interesting: writing a User Proposal [1] with it and a
> Jira issue [2] would be great
>
didn't have time today to be the fully compliant citizen (coherent
descriptions and patches), but I at least
Hervé BOUTEMY wrote:
>
> Forwarding this question to dev list...
>
Yay! I have the attention of the right person at the right time.
Hervé BOUTEMY wrote:
>
> archetype descriptor [2] should have goals
>
I'll dump related thoughts here:
* I like the ability to add goals in archetype descr
noticed different behavior when running <=beta-1 and this, I'm guessing it's
related to: http://jira.codehaus.org/browse/MNG-4615 ([regression] @required
plugin parameters are not validated)
the new behavior might actually be the desired behavior, not sure
from the plugin's plugin.xml:
I was wondering the exact same thing just yesterday, I ran into a project
using complie for several of its dependencies
--
View this message in context:
http://maven.40175.n5.nabble.com/Should-scope-names-be-validated-tp2266705p2266712.html
Sent from the Maven Developers mailing list archive at
mgainty wrote:
>
> http://news.bbc.co.uk/2/hi/world/us_and_canada/10564994.stm
>
So your theory is that she is/was a spy? Maybe from Ant?
I thought she might be a ghost, but newly gained empirical evidence leads me
to believe that she is a vampire. You may ask, "Who are you who are so wise
Barrie Treloar wrote:
>
> I wonder if this is her
> http://www.facebook.com/people/Julia-Antonova/1161441716
>
I think the most likely[1] answer is that she is a ghost[2, evidence] who
doesn't realize that out-of-office updates are no longer necessary.
Either way, if she is/isn't a ghost, I c
A couple of things to try:
Make sure you don't have the "bad" version of version 4.8.1
http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tt28385338.html#a28386276
Run tattletale to see where the junit classes are coming from, maybe you
have a duplicate from a repackaging coordinat
Tim O'Brien wrote:
>
> Ok, I'm glad we were all prepared for this. I've made sure to update
> the Maven FAQ to include this info for others that might be confused:
>
> http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova%2FTumlareoutoftheoffice%3F
>
looks like there is a
Wayne Fay wrote:
>
> You'd think Julia would eventually figure out that she should not be
> sending these out of office emails to public mailing lists... I guess
> not.
>
In her defense, her posts have always been helpful to me.
http://old.nabble.com/user/UserPosts.jtp?user=845884 her insight
Benjamin Bentmann wrote:
>
>
> Do we have some guideline for the deployed plugin site and its
> state/contents?
>
I really wish using ${project.version} in the site url pattern was a more
common practice.
--
View this message in context:
http://www.nabble.com/-maven-shade-plugin--Typo-in-
With the
org.eclipse.equinox
org.eclipse.equinox.app
example, it seems like the conventional configuration would become
someGroupId
${project.groupId}.someArtifactId.
Is that correct?
What should something like SWT look like?
org.eclipse.swt
org.e
13 matches
Mail list logo
