Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Baptiste Mathus]

Same here, good point. -gun.
B
Le 16 déc. 2014 22:46, "Matt Stephenson"  a écrit :

> A
>
> On Mon, Dec 15, 2014 at 2:39 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > After the run-off round, we are left with two names standing.
> >
> > This second vote will be a straight and simple majority wins.
> >
> > The vote will be open for at least 72 hours (with the potential of an
> > extension until I send a message saying that the polls are closed)
> >
> > There will be no discussion in this thread, we have talked it all enough
> > already. If you want to discuss something, please use a different thread.
> >
> > Vote:
> >
> > [A]: Shotgun
> > [B]: The Maven Owl
> >
> > Thank you very much for your time
> >
> > -Stephen
> >
>

Re: Little documentation issues

[Mirko Friedenhagen]

Barrie,

if I am not wrong you probably have it right ;-)

Regards
Mirko
-- 
Sent from my mobile
On Dec 17, 2014 3:46 AM, "Barrie Treloar"  wrote:

> On 17 December 2014 at 12:24, Ron Wheeler 
> wrote:
> >
> > One of the wonderful features about Maven is that no matter how long one
> > has been using it or how much one has studied Maven documentation , one
> > still feels the necessity of ending every assertion about how it works
> with
> > "(If I have that right.)" .
> >
> > I am so happy to not be alone!
>
>
> You are not the only one (If I have that right)
>

Re: Little documentation issues

[Barrie Treloar]

On 17 December 2014 at 12:24, Ron Wheeler 
wrote:
>
> One of the wonderful features about Maven is that no matter how long one
> has been using it or how much one has studied Maven documentation , one
> still feels the necessity of ending every assertion about how it works with
> "(If I have that right.)" .
>
> I am so happy to not be alone!


You are not the only one (If I have that right)

Re: Little documentation issues

[Ron Wheeler]

One of the wonderful features about Maven is that no matter how long one 
has been using it or how much one has studied Maven documentation , one 
still feels the necessity of ending every assertion about how it works 
with "(If I have that right.)" .


I am so happy to not be alone!

Ron

On 10/12/2014 10:48 AM, Mark H. Wood wrote:

Thinking about the developer's perspective a bit, I came up with some
suggestions but no actual language.

The developer is a person who wants to build units of software into
distributable products, so it's useful to talk briefly about
"lifecycle", "phase", "goal", "execution", and "artifact" in terms
familiar to such a person.  *Briefly* -- full details should be
linked.  This is simply to define terms which will then be used to map
the nature of "Maven plugin" to his experience.

A developer probably has a general notion of what a "plugin" is, so
what he needs is to know what a *Maven* plugin is: an assembly of Java
classes which provides additional concepts and behaviors that the
Maven framework can use in building your projects.  It can define
additional lifecycles and phases, and it provides goals that you may
bind to phases in order to perform additional work during the build.
There should be a link to how one creates a Maven plugin, elsewhere.

It may be well to mention at *this* point that much of Maven's
"built-in" behavior is actually provided by included plugins.  In this
way, one first learns what a Maven plugin is and then immediately sees
application of the concept through the lens of the knowledge one has
just gained.  Perhaps pick one common plugin as an example.

Someone noted that "goal" and "Mojo" are often used interchangeably,
but it may be good to mention here that "goal" is a named behavior and
"Mojo" is its implementation.  (If I have that right.)





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


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

Certificate problem with hostet Nexus

[Johannes Schneider]

Hey guys,


I have deployed the core.jar from processing.org to my own hostest nexus 
repository 
(https://nexus.cedarsoft.com/content/repositories/processing/org/processing/core/2.2.1/).


I have the following pom[1].
Running "mvn install" gives this output 
[2]:"java.security.cert.CertificateExpiredException: NotAfter: Thu Oct 
31 06:13:55 CET 2013"


I tried it on two different computers, same problem.
I am using Java 1.8.0_25 and Maven 3.2.3 using Linux.
I am using a startssl.com certificate. But I don't think this should be 
a problem, since I have other repositories (maven central mirror) that 
work fine.



Any ideas?


Thanks,

Johannes



[1]
-

http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>


  4.0.0

  com.cedarsoft
  processing-sample
  1.0.0-SNAPSHOT
  Processing Sample

  

  processing-repo

https://nexus.cedarsoft.com/content/repositories/processing

  

  

  org.processing
  core
  2.2.1
  test



  junit
  junit
  4.12
  test

  






[2]
---
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] 

[INFO] 


[INFO] Building processing-sample 1.0.0-SNAPSHOT
[INFO] 

Downloading: 
https://nexus.cedarsoft.com/content/repositories/processing/org/processing/core/2.2.1/core-2.2.1.pom
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 0.646 s
[INFO] Finished at: 2014-12-17T00:34:00+01:00
[INFO] Final Memory: 12M/303M
[INFO] 

[ERROR] Failed to execute goal on project processing-sample: Could not 
resolve dependencies for project 
com.cedarsoft:processing-sample:jar:1.0.0-SNAPSHOT: Failed to collect 
dependencies at org.processing:core:jar:2.2.1: Failed to read artifact 
descriptor for org.processing:core:jar:2.2.1: Could not transfer 
artifact org.processing:core:pom:2.2.1 from/to processing-repo 
(https://nexus.cedarsoft.com/content/repositories/processing): 
sun.security.validator.ValidatorException: PKIX path validation failed: 
java.security.cert.CertPathValidatorException: timestamp check failed: 
NotAfter: Thu Oct 31 06:13:55 CET 2013 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal on project processing-sample: Could not resolve 
dependencies for project 
com.cedarsoft:processing-sample:jar:1.0.0-SNAPSHOT: Failed to collect 
dependencies at org.processing:core:jar:2.2.1
	at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
	at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:483)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.project.D

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Matt Stephenson]

A

On Mon, Dec 15, 2014 at 2:39 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> After the run-off round, we are left with two names standing.
>
> This second vote will be a straight and simple majority wins.
>
> The vote will be open for at least 72 hours (with the potential of an
> extension until I send a message saying that the polls are closed)
>
> There will be no discussion in this thread, we have talked it all enough
> already. If you want to discuss something, please use a different thread.
>
> Vote:
>
> [A]: Shotgun
> [B]: The Maven Owl
>
> Thank you very much for your time
>
> -Stephen
>

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Mark Derricutt]

On 15 Dec 2014, at 23:39, Stephen Connolly wrote:

> [A]: Shotgun
> [B]: The Maven Owl

B.

-- 
Mark Derricutt
http://www.theoryinpractice.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt


signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Mirko Friedenhagen]

B

Regards
Mirko
-- 
Sent from my mobile
On Dec 15, 2014 11:40 AM, "Stephen Connolly" <
stephen.alan.conno...@gmail.com> wrote:

> After the run-off round, we are left with two names standing.
>
> This second vote will be a straight and simple majority wins.
>
> The vote will be open for at least 72 hours (with the potential of an
> extension until I send a message saying that the polls are closed)
>
> There will be no discussion in this thread, we have talked it all enough
> already. If you want to discuss something, please use a different thread.
>
> Vote:
>
> [A]: Shotgun
> [B]: The Maven Owl
>
> Thank you very much for your time
>
> -Stephen
>

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Alexis Morelle]

Changing to B + figured everyone would call it the Maven Owl anyway.

On 15/12/2014 14:02, Alexis Morelle wrote:

A

Alexis.

On 15/12/2014 11:39, Stephen Connolly wrote:

After the run-off round, we are left with two names standing.

This second vote will be a straight and simple majority wins.

The vote will be open for at least 72 hours (with the potential of an
extension until I send a message saying that the polls are closed)

There will be no discussion in this thread, we have talked it all enough
already. If you want to discuss something, please use a different 
thread.


Vote:

[A]: Shotgun
[B]: The Maven Owl

Thank you very much for your time

-Stephen




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






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

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Fábio Franco]

B
On Dec 16, 2014 4:42 AM, "Stephane Nicoll" 
wrote:

> On Mon, Dec 15, 2014 at 2:15 PM, Gary Gregory 
> wrote:
>
> > As "cute" as "Shutgun" might seem, for some unspecified definition of
> > "cute", I am sick of hearing about any kind of gun...
> >
> >
> http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html
>
>
> Same here. B
>
> >
> >
> > Gary
> >
> > On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek  wrote:
> > >
> > > B
> > >
> > > 2014-12-15 12:41 GMT+01:00 Martin Grigorov :
> > > > B
> > > >
> > > > Martin Grigorov
> > > > Wicket Training and Consulting
> > > > https://twitter.com/mtgrigorov
> > > >
> > > > On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly <
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >>
> > > >> A
> > > >>
> > > >> On 15 December 2014 at 10:39, Stephen Connolly <
> > > >> stephen.alan.conno...@gmail.com> wrote:
> > > >> >
> > > >> > After the run-off round, we are left with two names standing.
> > > >> >
> > > >> > This second vote will be a straight and simple majority wins.
> > > >> >
> > > >> > The vote will be open for at least 72 hours (with the potential of
> > an
> > > >> > extension until I send a message saying that the polls are closed)
> > > >> >
> > > >> > There will be no discussion in this thread, we have talked it all
> > > enough
> > > >> > already. If you want to discuss something, please use a different
> > > thread.
> > > >> >
> > > >> > Vote:
> > > >> >
> > > >> > [A]: Shotgun
> > > >> > [B]: The Maven Owl
> > > >> >
> > > >> > Thank you very much for your time
> > > >> >
> > > >> > -Stephen
> > > >> >
> > > >>
> > >
> > >
> > >
> > > --
> > > Vriendelijke groeten,
> > >
> > > Jeroen Hoek
> > >
> > > Lable
> > > ✉ jer...@lable.org
> > > ℡ 088 44 20 202
> > >
> > > http://lable.org
> > > KvK № 55984037
> > > BTW № NL8519.32.411.B.01
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition
> > 
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>

SCM config with *special* setup

[Melvyn de Kort]

Hello everybody,

My team is currently migrating a legacy Ant project with a bad Subversion 
layout to Maven.
We're running into 2 problems with the Maven scm configuration.
Let me first sketch the Subversion layout:

ROOT
  - trunk
  -- department
  - parent
- pom.xml
  - project1
- pom.xml (inherits parent)
  - project2
- pom.xml (inherits parent)
  - release
- pom.xml (inherits parent)
  - branches
- feature1
  - department
- parent
  - pom.xml
- project1
  - pom.xml (inherits parent)
- project2
  - pom.xml (inherits parent)
- release
  - pom.xml (inherits parent)
  - tags
- ...

When developping code, we work on branches, we then merge back to trunk and at 
some point we make a new branch from trunk for the release.
Since we have our trunk and branches on a higher level than the projects, we 
would have to add the branch name in the  URL to gain a full path.
Of course this is not what we want, because the Maven release plugin won't know 
how to make tags etc.
One possibility might be to use a compound of 2 variables (base url and branch 
name) and a relative path, but this feels like a very dirty workaround.
Does any of you have experience with a setup like this?

Kind regards,

Melvyn de Kort

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