Ahh, I misunderstood then, I though that every thing that were not in
compliance was commented out.
Looks really nice with the new simplified names.
2009/9/15 Jeremy Thomerson jer...@wickettraining.com:
Nino,
Thanks for taking a look at this. This is only half the battle, though.
Looking
You're still missing the point. Look at the following URL. See where it
says wicketstuff-jquery. This should be jquery. That's what caused the
confusion that started this thread. That's what should be fixed. I'm not
sure how many other projects do the same. Haven't had time to test.
No I understood what you said.. I'll fix them..
2009/9/15 Jeremy Thomerson jer...@wickettraining.com:
You're still missing the point. Look at the following URL. See where it
says wicketstuff-jquery. This should be jquery. That's what caused the
confusion that started this thread. That's
Ok fixed the jquery one.. Everybody else seems to comply (not having
contrib or stuff in their name), although alot of projects has a
naming like this : wicket-projectname
Im not sure if that fits the standard?
2009/9/15 nino martinez wael nino.martinez.w...@gmail.com:
No I understood what you
Btw went trough all the project.. There a lot of them these days.. I
should try some of them out :)
Although almost every of them are not described on the wicketstuff
wiki, that is sad (I know im one of the sinners aswell)..
This could be used as template page (although the part about maven are
Hmm seems the only one who are not compiling are ddcalendar.. The
other two are syringe and shiro-security, until their dependencies
become available..
There seems to be something here :
http://repository.apache.org/snapshots/org/apache/shiro/
Tauren mentioned that he would correct the pom..?
As Nino points out, Shiro does have a snapshot pom available now, but no
actual release version yet. I thought about adding the snapshot pom to
wicketstuff shiro-security, but the snapshot is rather bleeding edge and I
worry that it may not work at some point. Should I go ahead and do it
anyway?
You can add it if you'd like, but we can only release off of release
versions - maven won't let you do otherwise (as it's not wise). So, for our
snapshot releases - go for it. But please add a comment in the main
wicketstuff-core pom that mentions that it will not be able to be included
with
Nino,
Thanks for taking a look at this. This is only half the battle, though.
Looking back earlier in this thread, you'll see that the actual problem was
that jquery is not following the naming conventions in
/wicketstuff-core/jquery-parent/jquery/pom.xml it uses an artifact ID of
Let me see if I could do that in the coming weeks. However we could
have a red zone for projects that are becoming outdated.. If of course
there are any? Just to tell the authors that they are in danger of
being removed - attic.
2009/9/10 Jeremy Thomerson jer...@wickettraining.com:
In the time
Hi Jeremy
Should we have a list of offendending project?
2009/9/6 Jeremy Thomerson jer...@wickettraining.com:
First, jquery was built. They don't follow the naming conventions like they
should, so you have to look into the pom to realize that it's actually
wicketstuff-jquery [1].
Second,
In the time it would take to generate the list, you could fix the problems.
I wrote detailed instructions for adding projects to WS-core, so someone
should be able to take those and fix the projects that are not meeting those
standards.
You want to do it?
--
Jeremy Thomerson
So jquery-parent was build, which just references jquery and
jquery-examples - neither of which were build. Whats the point of
that?
Also, how can we get wicketstuff-merged-resources included in the next release?
Jörn
On Mon, Aug 31, 2009 at 10:20 PM, Jeremy
Thomersonjer...@wickettraining.com
First, jquery was built. They don't follow the naming conventions like they
should, so you have to look into the pom to realize that it's actually
wicketstuff-jquery [1].
Second, regarding merged resources - there's a link on the wiki [2] that
explains how. Please make sure to follow all
I successfully built Wicket Stuff Core 1.4.1 today. It is in the
(very very slow) process of doing a release:perform (currently
uploading all of the necessary files to wicketstuff repo). Hopefully
by the time you read this, your project will be available as 1.4.1.
Here are a couple that seem to
Hi Jeremy,
Great to see another release of Wicket Stuff Core !!
Some weeks ago you suggested :
I think that the best solution is that we have 1.4.1.X where X is our
release number.
Did you change your mind about this ?
http://www.mail-archive.com/users@wicket.apache.org/msg40780.html
Wicket Stuff Core 1.4.1 is now released:
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 204 minutes 20 seconds
[INFO] Finished at: Mon Aug 31 14:04:09 CDT 2009
[INFO] Final Memory: 218M/929M
[INFO]
very slow build :)
On Mon, Aug 31, 2009 at 9:07 PM, Jeremy
Thomersonjer...@wickettraining.com wrote:
Wicket Stuff Core 1.4.1 is now released:
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 204 minutes 20 seconds
I have the credentials and think that I will definitely be trying this on
the next release :)
--
Jeremy Thomerson
http://www.wickettraining.com
On Mon, Aug 31, 2009 at 3:16 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
Perhaps it's more beneficial to do the actual release local on
19 matches
Mail list logo
