Copying of the wepresources is done by the same plugin as the
packaging of the war. There is no way you can come in between that.
A possible solution would be too configure the war plugin to not copy
the resources you want to process and include the generated resources:
The Maven XML Beans Plugin team is pleased to announce the
xmlbeans-maven-plugin-2.3.3 release!
Runs the xmlbeans parser/code generator against schemas in files and dependent
jars.
Changes in this version include:
Fixed Bugs:
o Use a Resource instead of copying generated binary goo Issue: MX
Hi all.
I am trying to use Maven Embedder 3.0-alpha-2 (latest version to be found on the
central repository), and am running into a problem when running a build on a
specified POM (see code below) : the POM in question references artefacts which
are on our central Archiva repository, accessible by
Hi Folks,
What's the best way to handle javascript using Maven? I have searched
the ML archive but it seems all projects have sort of died
I have looked at javascript-maven-pluging [1]. But:
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site
I've used GWT w/ maven.
-Dave
On Mon, Sep 21, 2009 at 6:26 AM, Minto van der Sluis wrote:
> Hi Folks,
>
> What's the best way to handle javascript using Maven? I have searched the
> ML archive but it seems all projects have sort of died
>
> I have looked at javascript-maven-pluging [1]. But:
> -
I created the javascript-maven-pluging two years agoI didn't work on it
anymore for a while as I don't use it @work and have no more time left to
work on it
Patch are welcome if you'd like to support & improve it ;)
2009/9/21 Minto van der Sluis
> Hi Folks,
>
> What's the best way to handle jav
Minto van der Sluis wrote:
What's the best way to handle javascript using Maven? I have searched
the ML archive but it seems all projects have sort of died
I have looked at javascript-maven-pluging [1]. But:
- svn activity is near to none for the last year.
- sources and web-site seem to be out
Ow, this sourceFile is really painful =/ but flex compiler demands it and I
do my best to find the right one =D
FWIW, flexmojos should be looking the files content searching for the unique
Application before asking you the file. Did you had more then one
Application?
Anway I will try to impro
Same feedback from me. I got few users requesting status for the plugin (as
you do) and no contribution / proposal / support request in the plugin
Seems there is few maven user to build JS apps.
> None of the above projects are dead AFAIK. None of them tries to provide
> everything plus the kitc
Same for me with the maven-js-plugin. We have in the works more
features to implement but, I have much less time than I did when I
started on it. Also, there hasn't been much requested as has been
mentioned so anything we have come up for new features has just been
the result of brainstorming ins
Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)
A different look gives the following results:
javascript-maven-plugin
19 open issues/ total unknown (to me)
mailing list: (archive can't be found)
commiters: 4 (olamy,ndeloof,bentman,trygvis)
# commits
When I run 'mvn install' Maven looks outside for the files first, e.g.
http://org.apache.openejb, before it looks for the file in my local
nexus repository. I want Maven to look into my local Nexus Maven
Repository first.
Thankx,
Ashoo Oberoi.
Look at // in your pom.xml.
Should be "never" in this element.
Martin Schayna
Oberoi, Ashoo wrote:
When I run 'mvn install' Maven looks outside for the files first, e.g.
http://org.apache.openejb, before it looks for the file in my local
nexus repository. I want Maven to look into my local Nexu
Minto van der Sluis wrote:
Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)
Aren't we all ;-)
Lack of users has IMHO multiple causes:
1) Javascript source management is an afterthough on many project. They
include it as resources in their WAR project. (I've
I don't think GWT can manage existing JS files. GWT could be used for new
dev and the rest as a static resource which could be used by GWT if desired.
On Mon, Sep 21, 2009 at 9:26 AM, Minto van der Sluis wrote:
> Oeps, it seems I stepped on some to toes, sorry guys
> ... and that I am spoiled ;
Hi Martin,
I am not looking for a particular javascript library, I am looking for a
kind of dependency management as there exists for java projects. Both
javascript-maven-plugin as maven-jstools-plugin seem to be capable of
doing that.
On my current project I inherited a javascript mess wher
I have 4 poms:
1) parent, which has common dependencies and configuration shared by children
2) persistence, which packages a jar and is a child of parent
3) services, which packages a war, is a child of parent, and has persistence as
a dependency
4) logging, which packages a jar that is a depend
Hi Manos,
JavascriptDependencyFilter is a nice feature and a technical showcase,
but I would not allow a feature like that to be activated in projects I
control.
With this feature I have no absolute control over my deliverables. As
far as I can tell there is no garantee that 2 installations
Hello NG,
I plan to create a simple private maven repository from some of my libs. I
googled for instructions of how to create an repository but only found
guidance using repository manager like nexus or similar.
But I want to make it as easy as possible.
I have access to an webserver via sftp.
Greetings:
I'm trying to include the "test" sources into a maven repository but am
struggling getting them to generate. I want them to be included during the
'mvn release' targets, but so far they aren't. I've taken a look at the
maven-source-plugin documentation but haven't been able to piece
Hiyas,
I am trying to use the Maven War Plugin to move some resources into the
WEB-INF/xsd directory instead of the WEB-INF/classes directory...
The XSDs exist in the src/main/config directory along with some
descriptive xml files which I do not want copied. I configured the
Maven War Plug
Hi Neil,
I usually add a project for the distribution so that I can decouple the
"build logic" from the modules. In the parent I define the assembly plugin
and in this distribution module I write the assembly under
src/resources/assembly.
Using this approach will avoid weird situation where one
add a second execution with a configuration defining a different classifier
(test-src) and a different includes pattern
2009/9/21 Bill Brown
>
> Greetings:
>
> I'm trying to include the "test" sources into a maven repository but am
> struggling getting them to generate. I want them to be includ
I have that book, but it isn't clear to me if the assembly plugin actually
builds and installs all the components. The way it reads, it seems like you
simply describe where existing files live to be included in the assembly. It
doesn't seem to actually build the dependencies. Am I wrong on this?
Using Nexus or Artifactory is making it as easy as possible. They come
bundled with a web container, so you only have to unpack and run.
/Anders
On Mon, Sep 21, 2009 at 20:39, Thomas P wrote:
>
> Hello NG,
>
> I plan to create a simple private maven repository from some of my libs. I
> googled
(Not sure if I should take this discussion here or to dev, so I play safe and
start here.)
I'm a currently happy user of maven that's learning about Java Web Start,
pack200, and signed jars. Seems that to be able to sign *and* pack200 a jar,
you need to repack it using pack200 *before* signing. A
On 22/09/2009, at 4:39 AM, Thomas P wrote:
...
[INFO] [deploy:deploy {execution: default-deploy}]
Password for ...
Uploading: ...1.0.0.jar
63K uploaded (...-1.0.0.jar)
[INFO] Uploading project information for ... 1.0.0
Password for ...
[INFO] Retrieving previous metadata from private-repo
Pass
Try:
mvn help:effective-settings
and
mvn help:effective-pom
You will find that you probably have a element pointing
to OpenEJB.
If you want to restrict Maven to only look at your repository manager
you are better to use the mirror settings: http://maven.apache.org/guides/mini/guide-mirr
You need to add wagon-http-lightweight to the classpath along with the
embedder. However, I don't think that will guarantee that this works -
the last 3.0 embedder release is probably not stable enough.
You're better off directly using the maven-core library and
dependencies from 2.2.1 at t
On 12/09/2009, at 10:05 AM, jemmer wrote:
We are using a the reactor plugin extensively but have noticed that
it never
installs the master pom to the local repository. We manage all of our
dependency version information in the master pom, so it is important
that it
be updated in the rep
Folks;
maybe a strange use case again, however: We're using maven2 along with
Spring and some other libraries included to build web applications, deployed
to .war files, usually deployed to contain all the dependent .jars in
WEB-INF/lib. While this is good in most situations, we found that in one
I think you should have scope 'provided'. Your use case is what that's for.
Regarding handling your dependencies for production, that's more of a server
deployment issue isn't it? What I think you can use is the copy-dependensies
mojo of the dependency plugin (
http://maven.apache.org/plugins/mave
I'm not sure if you got this resolved but I'm told this is a server
side rule to prevent the bad checksums from 2.2.0 getting into the
repository. It may need to be reviewed - in any case you should
contact Atlassian about it as Maven is working with other WebDAV hosts..
- Brett
On 15/09/2
Hi Anders;
and first, thanks a bunch for your comments, much appreciated. :)
Anders Hammar schrieb:
> I think you should have scope 'provided'. Your use case is what that's for.
Yes, that's what I thought as well, but, well, it's not always the case -
we're using the same app code base for vario
>
> Anders Hammar schrieb:
> > I think you should have scope 'provided'. Your use case is what that's
> for.
>
> Yes, that's what I thought as well, but, well, it's not always the case -
> we're using the same app code base for various deployments, but in not all
> situations the artifacts actually
Anders Hammar schrieb:
> You can have one project with a primary artifact (including all
> dependencies) and an extra artifact (w/o deps) using a classifier. I don't
> think you should worry about have many artifacts. If you do that, then you
> will have problems with maven...:-)
I see. :) So by t
36 matches
Mail list logo
