> We have a project, JBoss Webservices. This project has one source tree
> and is set up as a single project.We build a jar using jdk1.5.
> Next we retrotranslate that jar to run on a 1.4 version jvm which
> produces a second artifact webservices1.4 version.Of course, this
> defies the one
> If possible, can u share with us the XSLT u wrote to convert POMv3 to POMv4?
How did I _know_ that question was coming? :-)
Please find it attached.
-- /v\atthew
http://www.w3.org/1999/XSL/Transform";>
http://maven.apache.org/POM/4.0.0
> He was lookin at the wrong plugin. It wasn't a problem of the pom v3
> but the plugin NOT working on maven 2, so no need for a m2 pom
I admit I hijacked this thread, but I did want to make mention of the
point while I was thinking about it.
When one specifies legacy, as is required sometimes, i
> When is the latest edition supporting POM v4.0.0 expected?
I wondered about this as well when I was trying to get the xdoclet2
maven2 plugin up and running. It would find poms, but they weren't
Maven2 poms and it was MOST upset.
It was my thought that either M2 take that logical step and say,
> The problem in this approach is that the ejb3 files and war files I
> created needs to be in repository. I don't want to do that because we
> will not need these files individually as par of any deployable.
That's not the spirit of Maven, since if _you_ wanted to use them, then
there is a chance
> was also defined as an alias in httpd.conf like
> alias /m2-repo /absolute/path/to/our/repository
> and I defined a element without any auth elements, just DAV On
>
> Depending on the url in the pom, I'm getting an authorization error (url of
> http://server:port/m2-repo)
If anyone else is interested in this drama, please vote for:
http://jira.codehaus.org/browse/WAGONHTTP-7
> wagon-http dos not handle HTTP 204 No Content code as success
http://jira.codehaus.org/browse/WAGONHTTP-8
> wagon-http does not MKCOL for missing parent resources during deploy
-- /v\atth
> > I found the instructions here to be useful:
> > http://jira.codehaus.org/browse/MNG-1580
> Webdav is supported now? since when? I was really waiting for that! thank!
Like I said, Maven hates us who don't want to futz with scp or ftp, but
we are smarter than it is!
The following was tested me
> It seems nobody has ever tried http.
That's certainly not true, but you are right that WebDAV support has
been very quiet on these lists.
I found the instructions here to be useful:
http://jira.codehaus.org/browse/MNG-1580
-- /v\atthew
---
> None of this is confidence inspiring. Does anyone have recommendations
> for a reliable release protocol with Windows on the client side?
After you futz around with it for a while, I believe WebDAV is a mature
transport upon which to build a Maven repo.
Please see http://jira.codehaus.org/brow
Through some magical means, one may reference POM elements in a
(formerly known as Jexl?) expression, such as
"${project.build.directory}". I was curious if one may reference the
declared (or implied!) plugins, or more specifically the configuration
properties of the plugins.
To make this more con
> Is it possible to add namespaces and make something like the following
> possible?
If I'm not mistaken, m2's pom does have namespaces. The root element is
in the 'http://maven.apache.org/POM/4.0.0' namespace. I'm not certain
how that impacts your real question, however.
> Allowing 1 line instea
> A screen scraper would be acceptable. This has been discussed but by the
> time we finally determined that I had lost interest.
I am an advocate of whatever steps we can take to make the end-user's
life easier, but I wanted to make an observation about that idea.
I don't believe it will be as
> The problem is that war uses the unsigned jars coming from the
> repository, instead of the signed jars.
There are two immediate fixes for this that I can think of:
Hackery: use the correct combination of and prereqs="" to cause
the 'jnlp' goal to run, a custom goal to copy the
${maven.build.
> it. We tend to check in our j2ee stuff for compilation purposes (and
> call it jsdk-24.jar, for example). We never deploy it (Resin takes
> care of providing the implementation).
Both the naming of the jar and your description of its use implies that
you want servlet-api-2.4 and maybe jsp-ap
> checkout maven-proxy
I wondered if I was going to get bombarded with that link. My interest
is Apache module centric. That's why I included the bit about the Python
server and not wanting to maintain yet-another-service, _especially_ a
servlet container.
I do appreciate your response, though, a
First, my objective. I want maven.repo.remote to point to our intranet
Apache server for all artifacts. If our intranet does not have the
artifact, it should connect to a "foreign" maven.repo.remote
(ibiblio.org for argument's sake) and fetch it, storing a copy of the
bytes as they fly by.
I have
> I'm a total newbie. I've installed Maven and CruiseControl
> according to their manuals, and they're working great on their own.
To stir another variable into the mix, LuntBuild
( http://luntbuild.sf.net/ ) alleges support for Maven projects. I
cannot vouch for it, but thought you might want
I googled for such a device but did not find anything. Is there a
mechanism for sending email from Maven 1? I am familiar with ant:mail,
but wondered if that was the right way or if there was a more Mavenized
method.
Thanks,
-- /v\atthew
---
>> Can you seperate out that EJB into its own EAR?
> We could do that. However, I think it would have a big impact on
> performance; we would need to use remote interfaces instead of local ones
I don't claim to be an EJB expert, but it is my understanding that Local
(vs Remote) is the distinction
> Since there is no standard JSPC, I would think that this belongs in a
> tomcat plugin.
I thought that Tomcat was the reference implementation for web-app
container, at least before Sun started shipping S1AS as the J2EE RI.
Even if not, it's a "reasonable" conclusion that Jasper is as close as
> > > I want to update all the default plugins for my Maven 1.0.2
> > > install. How can I force Maven to get the latest of all plugins?
> There is a list on the download page you can cut and paste from,
> that's as automatic as it gets in maven 1.0 :)
If you are handy with a scripting language,
> Is there an easy/built in way to include the dependency jar files when
> building a jar package? Or do I need to build my own plugin?
Sounds suspiciously like an EAR to me. If you ignore the
META-INF/application.xml, it's a zip file with all your jars packaged
together. That said, if you're "d
23 matches
Mail list logo
