I think the key is to leave metadata.xml and the latest snapshot in place
and just whack all the older ones.
On 11/28/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
Maven appears to key off the ordinal at the end of the snapshot name.
On 11/28/06, Jesse Kuhnert <[EMAIL PROTECTED] >
Maven appears to key off the ordinal at the end of the snapshot name.
On 11/28/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I did "reset" the snapshots. Felt like the directories were getting
overly large.
I wonder why maven won't resolve them regardless though?
On 11
It looks like the maven 4.1.1 SNAPSHOTs somehow started over as of November
25. The consequence seems to be that you don't automatically get the new
snapshot.The workaround is to whack the org/apache/tapestry section of your
maven repository.
-- Mark R
Jesse pointed out that it should be target= instead of element= when the
thing being listened to is a Tapestry component (i.e., has a jwcid).
Apparently, element= is for html elements that aren't tapestry components.
If the problem you are having is the same as mine (I think it might be) then
it
events="onchange",
submitForm="selectForm",
async=true)
public void cascadeDisks() {
debugCascade();
initModels();
getRequestCycle().getResponseBuilder().updateComponent("trackTable");
Here is my latest issue:
I am trying to use @EventListener to handle cascading dependencies in
PropertySelections. Imagine three PropertySelections in a form, representing
countries, regions, and cities respectively. When the user selects a
country, the regions list is populated with appropriate
istener on
the page class and make a call my component to let it know what changed. I
am sure there must be a better way that allows me to encapsulate all the
logic within my component, so if anyone can point me in the right direction,
that would be great.
On 11/24/06, Mark Reynolds <[EMAIL PROT
I am trying to create a reusuable component that encapsulates the
functionality of two related PropertySelection components.
I placed an @EventListerner annotation on a method inside of my component
class.
public abstract class MySelection extends BaseComponent {
@EventListener(events = "onc
Can you give explain what you mean by "there are ranges in the version
specifications" and perhaps give an example?
On 8/16/06, Konstantin Ignatyev wrote:
Rant:
Unfortunately Maven archichitecture and practices are
not allow repeatable builds because there are ranges
in the version specificatio
My opinion is that it's beta quality, or better. Jesse is fixing
everything that comes up super fast and putting out new snapshots all
the time. The great thing is if you build your project with Maven 2
and stay on the snapshots, you get the latest/greatest automatically.
-- Mark R
On 8/15/06, P
http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-examples/TimeTracker/
Shing Hing Man wrote:
Could someone please let me know where I can download
the source code for Tapestry4.1 TimeTracker demo ?
Shing
Home page :
http://uk.geocities.com/matmsh/index.html
Jesse,
The "action" parameter on the Submit component is marked as deprecated,
but with no explanation. Can you give us the low down?
Thanks.
-- Mark R
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
Using gmane, you can access any mirrored mailing list (including all
apache mailing lists):
* using a web-based threaded reader with search
* using a blog-like, flat interface with search
* using an NNTP news reader
* using any one of four variations of an rss feed
You can even search across
13 matches
Mail list logo
