On 4/20/06, Don Brown [EMAIL PROTECTED] wrote:
Can we require these snapshot plugins in our POM somehow?
I'm fine with working with snapshots, but their download and
use should be automatic.
When the Javadoc plugin gets fixed, yes. For now, the released
versions are working (you just don't
Can we require these snapshot plugins in our POM somehow? I'm fine with working with snapshots, but their download and
use should be automatic.
Don
Wendy Smoak wrote:
On 4/18/06, Don Brown [EMAIL PROTECTED] wrote:
We definitely need an action/src/site directory to contain
the root site.xml
On 4/14/06, Wendy Smoak [EMAIL PROTECTED] wrote:
... to get the Javadoc generated for the
site, add this to action/pom.xml:
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
On 4/18/06, Don Brown [EMAIL PROTECTED] wrote:
We definitely need an action/src/site directory to contain
the root site.xml that others inherit, and if you can get
over the aforementioned issue, then collecting all docs
there would work for me.
I moved action/core/src/site up to src/site,
I spent some time yesterday looking at what's left wrt the sample apps.
From struts/action/ I can execute the following:
$mvn (which runs the install target by default)
Looks like all artifacts are built correctly, so I proceeded to
deploy all of the web apps...
struts-cookbook
- was
Interesting that you would put [action1] in when discussing struts but not
[faces] when discussing faces. This is a real upside down deal, isn't it?
On 4/5/06, James Mitchell [EMAIL PROTECTED] wrote:
I'd like to address some the current [action 1] build issues. Now
that we've simplified the
On 4/14/06, James Mitchell [EMAIL PROTECTED] wrote:
I spent some time yesterday looking at what's left wrt the sample apps.
Thanks. :)
struts-mailreader
- good to go
(Does the web tests work for this yet?)
They're done with Canoo Webtest, right? I didn't find a m2 plugin for
it, but we
Another one from the chat log... to get the Javadoc generated for the
site, add this to action/pom.xml:
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
...
(and repeat for other reporting plugins.
On 4/5/06, James Mitchell [EMAIL PROTECTED] wrote:
So, is it 1.3.1 or 1.3.2?
The versions are correct. Struts Tiles has a separate build and is at
1.3.1-SNAPSHOT, having had a 1.3.0 test build. The Struts Action jars
(core, el, extras, taglib...) will be versioned together and should be
at
On 4/6/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 4/5/06, James Mitchell [EMAIL PROTECTED] wrote:
So, is it 1.3.1 or 1.3.2?
The versions are correct. Struts Tiles has a separate build and is at
1.3.1-SNAPSHOT, having had a 1.3.0 test build. The Struts Action jars
(core, el, extras,
James Mitchell wrote:
I'd like to address some the current [action 1] build issues. Now
that we've simplified the directory structure (thanks Don!), I'd like
to spend some time on our build process.
Please comment on the following, if I don't hear back soon I'll go
ahead and take care
Ok, I'm working with Wendy to do the Maven 2 conversion. Here is the plan we
have decided on:
1. All the jar artifacts (core, taglib, el, faces, scripting, extras) get
their own directory and pom
2. All the war artifacts, including the example apps from modules like faces and scripting,
On 4/6/06, Don Brown [EMAIL PROTECTED] wrote:
Ok, I'm working with Wendy to do the Maven 2 conversion. Here is the plan
we have decided on:
1. All the jar artifacts (core, taglib, el, faces, scripting, extras)
get their own directory and pom
2. All the war artifacts, including the
13 matches
Mail list logo
