Re: Trailing whitespace in Maven Core

[Michael Osipov]

Am 2014-11-23 um 18:09 schrieb Michael Osipov:

Am 2014-11-23 um 16:56 schrieb Hervé BOUTEMY:

Le dimanche 23 novembre 2014 15:58:56 Michael Osipov a écrit :

Hi folks,

while merging my local Git clone of maven.git I have noticed that some
trailing whitespace has been added to the repo. I performed some shell

magic:
  > find . -type f -name '*.' -exec grep -E -l " +$" {} \; |

xargs -I{} sed -i -e 's/ \+$//' {}

I have pushed the branch 'trailing-whitespace':
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=0343c5260

1f7623415511e4f05fc79b03c283455

I ran Maven Integration Testing on the bin tarball and haven't noticed
any further ITs failing beside those which fail with master anyway.

Is anyone opposed if I merge the branch into master?

the only issue I see is that trailing spaces from javadoc comments will
reappear
but on other places, this is a little improvement IMHO
so I have no problem with this


While the Javadoc issue is true, it makes no sense to go over the add
interactively. To tedious.

I'll wait a day or two and will proceed with the merge.


Pushed: 
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=0343c52601f7623415511e4f05fc79b03c283455




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Abandoned bugs analysis

[Michael Osipov]

Am 2014-11-24 um 23:05 schrieb Michael Osipov:

Hi folks,

I ran this query in JIRA: project in
projectsWhereUserHasPermission("Administer Projects") AND updated <=
"2012-12-31" and resolution = Unresolved and type = Bug ORDER BY created
desc

Bugs which haven't been touched for almost two years. Total amount:
*1139*. A lot of them are still Maven 1.x related 8-).

Is there someone with bulk change abilities able to close those as
"Won't Fix" with a note like: Big clean up end of 2014, you think that
this issue still persists, reopen it?


It seems like I have those abilities too directly from the queries page.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Abandoned bugs analysis

[Michael Osipov]

Hi folks,

I ran this query in JIRA: project in 
projectsWhereUserHasPermission("Administer Projects") AND updated <= 
"2012-12-31" and resolution = Unresolved and type = Bug ORDER BY created 
desc


Bugs which haven't been touched for almost two years. Total amount: 
*1139*. A lot of them are still Maven 1.x related 8-).


Is there someone with bulk change abilities able to close those as 
"Won't Fix" with a note like: Big clean up end of 2014, you think that 
this issue still persists, reopen it?


What do you think?

Michael

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] Idle bug handling approach

[Michael Osipov]

Folks,

here is a little wrap up after the ideas and votes posted so far:

1. Ask for additional information if you think you can fix that bug or 
want to help someone else to drag some attention

2. Give the reporter 30 days
3. Add a reminder after 30 days for a grace period of 10 days
4. 10 days have passed and no change has happened, close as "Incomplete"

Did I miss something?

I would this to the Development Center page in time.

Michael

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: New logo?

[Martin Todorov]

Hi,

I've been thinking -- whatever the animal (owl, or not), it would be really
cool if it's wearing some sort of super-hero outfit with the letter "M".
After all, it's been Maven that has brought super-powers (and order) to our
builds... :-)

Just my my proposal...

Cheers,

Martin




On Mon, Nov 24, 2014 at 3:22 AM, Paul Benedict  wrote:

> Will the graphic be in PNG format so the "shotgun" stomach can be
> transparent.?
>
>
> Cheers,
> Paul
>
> On Sun, Nov 23, 2014 at 9:11 PM, Ralph Goers 
> wrote:
>
> > I like the owl, but why not just make the body a solid color?  To me it
> > now looks like one of those fancy “haircuts’ people get where they have
> > something shaved into their head.
> >
> > Ralph
> >
> > > On Nov 20, 2014, at 2:43 AM, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> > >
> > > Stop calling Couché-tard "shotgun owl"!
> > >
> > > Does this make it clearer that it's a feather patch:
> > >
> > >
> >
> http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-4-large.png
> > >
> > > On 19 November 2014 21:19, Dan Rollo  wrote:
> > >
> > >> Looks great!  Before reading the comet below, I had the same “shotgun”
> > >> thought about the white chest patch. Would it help if the white oval
> > moved
> > >> up, and started at the scarf? (Basically the top of the oval hidden
> > under
> > >> the scarf?)
> > >>
> > >> Understood about the “design by committee”.
> > >>
> > >> Dan
> > >>
> > >>
> > >>
> > >> From: Andreas Gudian 
> > >> Subject: Re: New logo?
> > >> Date: November 19, 2014 at 12:49:59 PM EST
> > >> To: Maven Developers List 
> > >>
> > >>
> > >> I like it. Cute but resolute birdy, and the font looks fresh and
> modern.
> > >>
> > >> But wait - did someone shoot a hole right through the owl? You can
> even
> > see
> > >> the shadow behind it. ;-) Maybe the patch in the middle could be a
> > little
> > >> darker, perhaps with a hint/tint of the surrounding colour?
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: Jigsaw early-access builds updated (JDK 9 build 40)

[tibor17]

@Rory
The Maven should provide built-support for Jigsaw modules.
Has this activity already started?



-
BR, tibor17
--
View this message in context: 
http://maven.40175.n5.nabble.com/Jigsaw-early-access-builds-updated-JDK-9-build-40-tp581p5815585.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: How to setup SVN for HTML content of published site?

[Martin Gainty]

> Date: Mon, 24 Nov 2014 08:32:46 -0700
> From: tibo...@lycos.com
> To: dev@maven.apache.org
> Subject: How to setup SVN for HTML content of published site?
> 
> I want to deploy the site to SVN repo. 
> How to configure the SVN server so that the path in particular repository
> would be provided like a web content?

MG>I do not know of a SVN server which serves web-content per-se..perhaps the 
other devs can suggest?
MG>nexus installs an instance of Eclipse-Jetty web-server which you can monitor 
at localhost:8081
MG>https://github.com/sonatype/nexus-book/blob/master/chapter-installation.asciidoc

> We are using CollabNet SubversionEdge.
> 
> 
> 
> -
> BR, tibor17
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/How-to-setup-SVN-for-HTML-content-of-published-site-tp5815564.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  

Re: Jigsaw early-access builds updated (JDK 9 build 40)

[Rory O'Donnell Oracle, Dublin ireland]

The purpose of my email was to invite you to test the early access builds
and report any issues/questions/suggestions on the jigsaw-dev 
 mailing list

or you can log bug reports via bugs.java.com .

Rgds,Rory

On 11/24/14 03:22 PM, tibor17 wrote:

@Rory
Would it mean that the Maven is going to die after Java 9 ?



-
BR, tibor17
--
View this message in context: 
http://maven.40175.n5.nabble.com/Jigsaw-early-access-builds-updated-JDK-9-build-40-tp581p5815558.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



--
Rgds,
Rory O'Donnell

Senior Quality Engineering Manager
Java Platform Group
Oracle EMEA , Block P5,
East Point Business Park, Dublin 3
Phone: +353 (0)1 8033887

How to setup SVN for HTML content of published site?

[tibor17]

I want to deploy the site to SVN repo. 
How to configure the SVN server so that the path in particular repository
would be provided like a web content?
We are using CollabNet SubversionEdge.



-
BR, tibor17
--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-setup-SVN-for-HTML-content-of-published-site-tp5815564.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Jigsaw early-access builds updated (JDK 9 build 40)

[tibor17]

@Rory
Would it mean that the Maven is going to die after Java 9 ?



-
BR, tibor17
--
View this message in context: 
http://maven.40175.n5.nabble.com/Jigsaw-early-access-builds-updated-JDK-9-build-40-tp581p5815558.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Jigsaw early-access builds updated (JDK 9 build 40)

[Rory O'Donnell]

Hi Robert & Kristian,

JDK 9 Early Access with Project Jigsaw build b40 is available for 
download at :

https://jdk9.java.net/jigsaw/

The goal of Project Jigsaw [2] is to design and implement a standard module
system for the Java SE Platform, and to apply that system to the 
Platform itself

and to the JDK.

The main change in this build is that it includes the jrt: file-system 
provider,

so it now implements all of the changes described in JEP 220.

Please refer to Project Jigsaw's updated project pages [2] & [4] and Mark
Reinhold's update [5] for further details.

We are very interested in your experiences testing this build. Comments,
questions, and suggestions are welcome on the jigsaw-dev 
 mailing list or

through bug reports via bugs.java.com .

Note: If you haven't already subscribed to that mailing list then please do
so first, otherwise your message will be discarded as spam.

Rgds, Rory

[1] https://jdk9.java.net/jigsaw/
[2] http://openjdk.java.net/projects/jigsaw/
[3] http://openjdk.java.net/jeps/220
[4] http://openjdk.java.net/projects/jigsaw/ea
[5] 
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2014-November/004014.html


--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: Maven-EJB-Plugin Problem maven-archiver upgrade 2.5 => 2.6

[Anders Hammar]

Hmm, Googel decided to send my mail before I finished...

> I ran into something similar in the maven-war-project. Checking I see that
> similar hard-coded values exist there:
>

Here's the link:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-plugin/src/test/java/org/apache/maven/plugin/war/stub/MavenProjectBasicStub.java?view=markup

I didn't bother to dig into this when I saw the issues but just fixed the
ITs.

/Anders



>
> On Mon, Nov 24, 2014 at 9:03 AM, Karl Heinz Marbaise 
> wrote:
>
>> Hi,
>>
>> so after diving more into this issue i found that the original
>> MavenProject is working different than the implemented Stub
>> (MavenProjectBasicStub), cause the MavenProject#getArtifactId() method
>> looks like this:
>>
>> public String getArtifactId()
>> {
>> return getModel().getArtifactId();
>> }
>>
>> in contrary the implemented Stub method of 
>> MavenProjectBasicStub#getArtifactId()
>> looks like this:
>>
>> public String getArtifactId()
>> {
>> return "maven-resource-plugin-test#" + identifier;
>> }
>>
>> which is not the same behaviour so i decided to change the Stub to behave
>> exactly like the original above and the result is as expected that the
>> tests now are working for both versions. maven-archiver 2.5 and 2.6.
>>
>> I have also changed the behaviour of the getGroupId() of the stub to
>> behave exactly like the original...
>>
>> This will solve my problem...
>>
>> Many thanks for your patience.and attention...
>>
>>
>> Kind regards
>> Karl Heinz Marbaise
>> On 11/23/14 9:39 PM, Karl Heinz Marbaise wrote:
>>
>>> Hi,
>>>
>>> On 11/23/14 10:27 AM, Michael Osipov wrote:
>>>
 Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:

> Hi,
>
> i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
> maven-archiver-2.6and i'm currently faced with a puzzling
> situation...
>
> If i update to 2.6 several tests will fail...
>
> For the tests there were stubs generated which using groupId/artifactId
> etc. but if i update to 2.6 it looks like the defined ModelStub (which
> contains artifactId etc.) seemed to be ignored and the
> MavenProjectBasicStub.java takes over which means the ModelStub is
> ignored (in some way)...
>
> If i change MavenProjectBasicStub.java accordingly my tests will
> work...
>
> Does someone has an idea which can explain this?
>

 Can you share the problematic logfile or point to a Jenkins job log?

>>>
>>> Sorry...sure i can
>>>
>>> I've maded a test project separately from SVN check in...
>>>
>>> The branch upgrade contains log files and a pom which has been changed
>>> to use maven-archiver-2.6 instead of 2.5 (the master contains unchanged
>>> state):
>>>
>>> https://github.com/khmarbaise/maven-ejb-plugin/tree/upgrade
>>>
>>> This branch includes a log file after i made the upgrade and run
>>>
>>> mvn -Prun-its clean verify
>>>
>>> https://github.com/khmarbaise/maven-ejb-plugin/blob/upgrade/mvn-2.6.log
>>>
>>>
>>> If i change the following lines it will run the tests without any
>>> issue...
>>>
>>>
>>> diff --git
>>> a/src/test/java/org/apache/maven/plugin/ejb/stub/
>>> MavenProjectBasicStub.java
>>> b/src/test/java/org/apache/maven/plugin/ejb/stub/
>>> MavenProjectBasicStub.java
>>> index d88274a..a268c20 100644
>>> ---
>>> a/src/test/java/org/apache/maven/plugin/ejb/stub/
>>> MavenProjectBasicStub.java
>>> +++
>>> b/src/test/java/org/apache/maven/plugin/ejb/stub/
>>> MavenProjectBasicStub.java
>>> @@ -117,12 +117,14 @@ public class MavenProjectBasicStub
>>>
>>>   public String getGroupId()
>>>   {
>>> -return "org.apache.maven.plugin.test";
>>> +//return "org.apache.maven.plugin.test";
>>> +return "org.apache.maven.test";
>>>   }
>>>
>>>   public String getArtifactId()
>>>   {
>>> -return "maven-resource-plugin-test#" + identifier;
>>> +return "maven-test-plugin";
>>> +//return "maven-resource-plugin-test#" + identifier;
>>>   }
>>>
>>>   public String getPackaging()
>>>
>>>
>>> It looks like (somehow) that the ModelStub is simply ignored...which
>>> don't understand at the moment and why? So this change in maven-archiver
>>> changes the behaviour in tests..? Plexus Injection ?
>>> Classloader issue ? Test Case setup ?
>>>
>>> I'm open for any suggestions...
>>>
>>> Thanks in advance.
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

Re: Maven-EJB-Plugin Problem maven-archiver upgrade 2.5 => 2.6

[Anders Hammar]

I ran into something similar in the maven-war-project. Checking I see that
similar hard-coded values exist there:

On Mon, Nov 24, 2014 at 9:03 AM, Karl Heinz Marbaise 
wrote:

> Hi,
>
> so after diving more into this issue i found that the original
> MavenProject is working different than the implemented Stub
> (MavenProjectBasicStub), cause the MavenProject#getArtifactId() method
> looks like this:
>
> public String getArtifactId()
> {
> return getModel().getArtifactId();
> }
>
> in contrary the implemented Stub method of 
> MavenProjectBasicStub#getArtifactId()
> looks like this:
>
> public String getArtifactId()
> {
> return "maven-resource-plugin-test#" + identifier;
> }
>
> which is not the same behaviour so i decided to change the Stub to behave
> exactly like the original above and the result is as expected that the
> tests now are working for both versions. maven-archiver 2.5 and 2.6.
>
> I have also changed the behaviour of the getGroupId() of the stub to
> behave exactly like the original...
>
> This will solve my problem...
>
> Many thanks for your patience.and attention...
>
>
> Kind regards
> Karl Heinz Marbaise
> On 11/23/14 9:39 PM, Karl Heinz Marbaise wrote:
>
>> Hi,
>>
>> On 11/23/14 10:27 AM, Michael Osipov wrote:
>>
>>> Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:
>>>
 Hi,

 i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
 maven-archiver-2.6and i'm currently faced with a puzzling
 situation...

 If i update to 2.6 several tests will fail...

 For the tests there were stubs generated which using groupId/artifactId
 etc. but if i update to 2.6 it looks like the defined ModelStub (which
 contains artifactId etc.) seemed to be ignored and the
 MavenProjectBasicStub.java takes over which means the ModelStub is
 ignored (in some way)...

 If i change MavenProjectBasicStub.java accordingly my tests will work...

 Does someone has an idea which can explain this?

>>>
>>> Can you share the problematic logfile or point to a Jenkins job log?
>>>
>>
>> Sorry...sure i can
>>
>> I've maded a test project separately from SVN check in...
>>
>> The branch upgrade contains log files and a pom which has been changed
>> to use maven-archiver-2.6 instead of 2.5 (the master contains unchanged
>> state):
>>
>> https://github.com/khmarbaise/maven-ejb-plugin/tree/upgrade
>>
>> This branch includes a log file after i made the upgrade and run
>>
>> mvn -Prun-its clean verify
>>
>> https://github.com/khmarbaise/maven-ejb-plugin/blob/upgrade/mvn-2.6.log
>>
>>
>> If i change the following lines it will run the tests without any issue...
>>
>>
>> diff --git
>> a/src/test/java/org/apache/maven/plugin/ejb/stub/
>> MavenProjectBasicStub.java
>> b/src/test/java/org/apache/maven/plugin/ejb/stub/
>> MavenProjectBasicStub.java
>> index d88274a..a268c20 100644
>> ---
>> a/src/test/java/org/apache/maven/plugin/ejb/stub/
>> MavenProjectBasicStub.java
>> +++
>> b/src/test/java/org/apache/maven/plugin/ejb/stub/
>> MavenProjectBasicStub.java
>> @@ -117,12 +117,14 @@ public class MavenProjectBasicStub
>>
>>   public String getGroupId()
>>   {
>> -return "org.apache.maven.plugin.test";
>> +//return "org.apache.maven.plugin.test";
>> +return "org.apache.maven.test";
>>   }
>>
>>   public String getArtifactId()
>>   {
>> -return "maven-resource-plugin-test#" + identifier;
>> +return "maven-test-plugin";
>> +//return "maven-resource-plugin-test#" + identifier;
>>   }
>>
>>   public String getPackaging()
>>
>>
>> It looks like (somehow) that the ModelStub is simply ignored...which
>> don't understand at the moment and why? So this change in maven-archiver
>> changes the behaviour in tests..? Plexus Injection ?
>> Classloader issue ? Test Case setup ?
>>
>> I'm open for any suggestions...
>>
>> Thanks in advance.
>> Kind regards
>> Karl Heinz Marbaise
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Graphic Design Assistance?

[Benson Margulies]

On Mon, Nov 24, 2014 at 3:26 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Benson,
>
> This sounds a bit like a case of owl or nothing...
>




>
>
> * We can see if there are any other of the submissions we received for the
> contest we ran and do a vote off
>
> * we can try and reboot the contest again; or
>
> * we can see if the community is happy with "shotgun the (mostly) friendly
> owl" ;-) and Alte Haas Grotesk Bold Italic
>
> * a final option would be to see if branding could give us a couple of
> hundred dollars to run a design contest on one of the design contest
> sites... When I looked into that option I came to the conclusion that we'd
> either need to get very lucky or we'd need to give a reasonably constrained
> brief as to what we want in a logo & mascot Otherwise we risk
> inappropriate use of Native American imagery (or if that's not an issue we
> could use the teepee logo I designed)... Or we end up with a logo that has
> no meaning for the project
>

Here is probably the only place I disagree with you. Good logo's don't have
to start life with meaning; they have to start life as memorable, and then
they acquire meaning by association. Maybe the felix.apache.org logo
resulted from some concept, maybe not, but to me it's purely a distinctive
graphic with at most, a diffuse relationship to content.

Or look at accumulo, which is 'typography + decoration.' The decoration
has, again, a very abstract relationship to the contents.


>
> Right now, my feeling is that the contest ran its course... I really would
> have liked the teepee logo with the feather v... Using just the teepee as a
> mascot... But after taking on board the concerns over usage of Native
> American imagery... After finding other "maven" companies using raven
> logos... My considered opinion is the owl is the best we have
>
> I don't have the energy to do anything other than call a vote to adopt the
> owl and my suggested logo... So if people want to explore the other
> options, please step up speak out and run with it!
>
> If nobody speaks out in the next couple of days I'll call the vote
> (if that would mean a vote over the US centric holiday, I think the vote
> should last a bit longer than 72h)
>

And I'll probably vote for it. The Owl is a big improvement over the
current situation; I wanted to know what our options were.



>
> -Stephen
>
>
> On Monday, November 24, 2014, Sally Khudairi
>  wrote:
>
>> Hey Benson --thanks so much for your note.
>>
>> Unfortunately, our donated resources are extremely limited; I'm not sure
>> how we'll be proceeding with the proposed Foundation work given the level
>> of feedback to incorporate.
>>
>> Having said that, several Apache projects, such as Logging, were seeking
>> a new logo for Log4j 2 and put a call for help from the public
>> https://t.co/p633jVyld9 --I'll be happy to help spread the word and
>> assist however needed.
>>
>> Warmly,
>> Sally
>>
>>
>> [From the mobile; please excuse top-posting, spelling/spacing errors, and
>> brevity]
>>
>> - Reply message -
>> From: "Benson Margulies" 
>> To: "Sally Khudairi" , "Maven Developers List" <
>> dev@maven.apache.org>
>> Subject: Graphic Design Assistance?
>> Date: Sun, Nov 23, 2014 21:50
>>
>> Sally,
>> The Maven community would like to update and improve its graphic design.
>> I wondered, based on the work on the overall Foundation site, where there
>> was any donated professional assistance of this kind available to
>> individual communities. We have some volunteer efforts in the direction of
>> a logo/mascot, but we wonder if any assistance is to be had.
>>
>> --benson
>
>
>
> --
> Sent from my phone
>

Re: Maven-EJB-Plugin Problem maven-archiver upgrade 2.5 => 2.6

[Karl Heinz Marbaise]

Hi,

so after diving more into this issue i found that the original 
MavenProject is working different than the implemented Stub 
(MavenProjectBasicStub), cause the MavenProject#getArtifactId() method 
looks like this:


public String getArtifactId()
{
return getModel().getArtifactId();
}

in contrary the implemented Stub method of 
MavenProjectBasicStub#getArtifactId() looks like this:


public String getArtifactId()
{
return "maven-resource-plugin-test#" + identifier;
}

which is not the same behaviour so i decided to change the Stub to 
behave exactly like the original above and the result is as expected 
that the tests now are working for both versions. maven-archiver 2.5 and 
2.6.


I have also changed the behaviour of the getGroupId() of the stub to 
behave exactly like the original...


This will solve my problem...

Many thanks for your patience.and attention...


Kind regards
Karl Heinz Marbaise
On 11/23/14 9:39 PM, Karl Heinz Marbaise wrote:

Hi,

On 11/23/14 10:27 AM, Michael Osipov wrote:

Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:

Hi,

i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling
situation...

If i update to 2.6 several tests will fail...

For the tests there were stubs generated which using groupId/artifactId
etc. but if i update to 2.6 it looks like the defined ModelStub (which
contains artifactId etc.) seemed to be ignored and the
MavenProjectBasicStub.java takes over which means the ModelStub is
ignored (in some way)...

If i change MavenProjectBasicStub.java accordingly my tests will work...

Does someone has an idea which can explain this?


Can you share the problematic logfile or point to a Jenkins job log?


Sorry...sure i can

I've maded a test project separately from SVN check in...

The branch upgrade contains log files and a pom which has been changed
to use maven-archiver-2.6 instead of 2.5 (the master contains unchanged
state):

https://github.com/khmarbaise/maven-ejb-plugin/tree/upgrade

This branch includes a log file after i made the upgrade and run

mvn -Prun-its clean verify

https://github.com/khmarbaise/maven-ejb-plugin/blob/upgrade/mvn-2.6.log


If i change the following lines it will run the tests without any issue...


diff --git
a/src/test/java/org/apache/maven/plugin/ejb/stub/MavenProjectBasicStub.java
b/src/test/java/org/apache/maven/plugin/ejb/stub/MavenProjectBasicStub.java
index d88274a..a268c20 100644
---
a/src/test/java/org/apache/maven/plugin/ejb/stub/MavenProjectBasicStub.java
+++
b/src/test/java/org/apache/maven/plugin/ejb/stub/MavenProjectBasicStub.java
@@ -117,12 +117,14 @@ public class MavenProjectBasicStub

  public String getGroupId()
  {
-return "org.apache.maven.plugin.test";
+//return "org.apache.maven.plugin.test";
+return "org.apache.maven.test";
  }

  public String getArtifactId()
  {
-return "maven-resource-plugin-test#" + identifier;
+return "maven-test-plugin";
+//return "maven-resource-plugin-test#" + identifier;
  }

  public String getPackaging()


It looks like (somehow) that the ModelStub is simply ignored...which
don't understand at the moment and why? So this change in maven-archiver
changes the behaviour in tests..? Plexus Injection ?
Classloader issue ? Test Case setup ?

I'm open for any suggestions...

Thanks in advance.
Kind regards
Karl Heinz Marbaise



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Graphic Design Assistance?

[Stephen Connolly]

Benson,

This sounds a bit like a case of owl or nothing...

* We can see if there are any other of the submissions we received for the
contest we ran and do a vote off

* we can try and reboot the contest again; or

* we can see if the community is happy with "shotgun the (mostly) friendly
owl" ;-) and Alte Haas Grotesk Bold Italic

* a final option would be to see if branding could give us a couple of
hundred dollars to run a design contest on one of the design contest
sites... When I looked into that option I came to the conclusion that we'd
either need to get very lucky or we'd need to give a reasonably constrained
brief as to what we want in a logo & mascot Otherwise we risk
inappropriate use of Native American imagery (or if that's not an issue we
could use the teepee logo I designed)... Or we end up with a logo that has
no meaning for the project

Right now, my feeling is that the contest ran its course... I really would
have liked the teepee logo with the feather v... Using just the teepee as a
mascot... But after taking on board the concerns over usage of Native
American imagery... After finding other "maven" companies using raven
logos... My considered opinion is the owl is the best we have

I don't have the energy to do anything other than call a vote to adopt the
owl and my suggested logo... So if people want to explore the other
options, please step up speak out and run with it!

If nobody speaks out in the next couple of days I'll call the vote (if that
would mean a vote over the US centric holiday, I think the vote should last
a bit longer than 72h)

-Stephen

On Monday, November 24, 2014, Sally Khudairi
 wrote:

> Hey Benson --thanks so much for your note.
>
> Unfortunately, our donated resources are extremely limited; I'm not sure
> how we'll be proceeding with the proposed Foundation work given the level
> of feedback to incorporate.
>
> Having said that, several Apache projects, such as Logging, were seeking a
> new logo for Log4j 2 and put a call for help from the public
> https://t.co/p633jVyld9 --I'll be happy to help spread the word and
> assist however needed.
>
> Warmly,
> Sally
>
>
> [From the mobile; please excuse top-posting, spelling/spacing errors, and
> brevity]
>
> - Reply message -
> From: "Benson Margulies" >
> To: "Sally Khudairi" >, "Maven Developers
> List" >
> Subject: Graphic Design Assistance?
> Date: Sun, Nov 23, 2014 21:50
>
> Sally,
> The Maven community would like to update and improve its graphic design. I
> wondered, based on the work on the overall Foundation site, where there was
> any donated professional assistance of this kind available to individual
> communities. We have some volunteer efforts in the direction of a
> logo/mascot, but we wonder if any assistance is to be had.
>
> --benson



-- 
Sent from my phone