Is the parent pom being resolved?
One of the legacies of the maven repo that sun set up is that you can have
a few hoops to jump through.
I'd ask the Hudson project (is it anyone besides Winston these days? -
asked from somebody very firmly on the Jenkins side of the split)
On Friday, 12 July 20
From my observation, in POM file and settings.xml don't do any config about
repository, the following are two files content :
In the end, i pastes the more detail debug infor of running 'mvn '.
1.Project POM file content :
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLS
I want to include just one artifact from the dependencies in the the result
jar, so my assembly descriptor:
/
org.example:test:zip:1.0.0
In the result jar I am able to see only example-test.zip artifact, no
project artifact. Looks like useProjectArtifact doesn't work (default
Hi,
src/main/config actually is the default/recommended place.
See
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
Not sure though it's a directory used by any plugin in general. But that
might not be an issue for you.
Cheers
2013/7/11 Russell Gol
Hi Richard,
You can use the property${basedir} to refer to root of the project, so
the directory in question would be ${basedir}/src/main/config
- Russ
On Jul 11, 2013, at 1:24 AM, "Richard Sand" wrote:
> I've several projects that were created before we began using maven and
> which
It could be configured either in your POM or your settings.xml.
On Jul 11, 2013, at 6:04 AM, 邹志勇 wrote:
> I don't config repository and where can i see the repository configured?
>
> Thanks.
>
>
> At 2013-07-11 09:46:57,"邹志勇" wrote:
>
> Hi,
> After i run the command 'mvn package', then i ge
I don't config repository and where can i see the repository configured?
Thanks.
At 2013-07-11 09:46:57,"邹志勇" wrote:
Hi,
After i run the command 'mvn package', then i get the following error message :
Failed to execute goal org.kohsuke:access-modifier-checker:1.4:enforce
(default-enforce) on
Couldn't find it there either...
Also the spec does not allow the use of an EL in the persistence.xml, so
you can't even delegate to JNDI or system properties... only hope is
container specific overriding via deployment descriptors
OpenEJB (the good guy) supports this:
http://tomee.apache.org/alt
It's not an EJB 3.1 thing... checking the 3.2 spec now
On 11 July 2013 10:22, christofer.d...@c-ware.de
wrote:
> Well it should be possible as the PersistenceUnitManager is more a JPA
> Thing and not restricted to Spring. In my example it is just configured
> using Spring. Think it should be pos
Well it should be possible as the PersistenceUnitManager is more a JPA Thing
and not restricted to Spring. In my example it is just configured using Spring.
Think it should be possible to do this an a JavaEE application (Perhaps I
should find this out somehow and extend my tutorial). If someone
That looks like a Spring only solution I wonder is there a pure JavaEE
counterpart
On 11 July 2013 09:56, christofer.d...@c-ware.de
wrote:
> You could have a look at my Wiki article about multiple persistence.xml
> files:
> https://dev.c-ware.de/confluence/display/PUBLIC/Multiple+persistence
You could have a look at my Wiki article about multiple persistence.xml files:
https://dev.c-ware.de/confluence/display/PUBLIC/Multiple+persistence.xml+in+a+multi-module+application
Here you could separate your JPA entities from the platform dependent Options.
In your case you could create your
Hi Richard,
> I can see it both ways... If it runs at
> the packaging phase, it'll start (by default) by processing the packaged
> artifact created by the default packaging and either overwriting the
> artifact or creating a new one with a classifier (e.g. "-small").
> If it runs at the pre-packag
13 matches
Mail list logo
