Hello,
You shouldn't have to do anything other than make the change to have it
propogated into maven. The tinymce artifact is already being
distributed as part of wicketstuff-core.
This is the current branch tracking wicket 1.4-SNAPSHOT:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4/
If you can get the changes in soon they can be included in the 1.4.13
release or in a 1.4.13.1 point release a little bit later (i.e. when you
tell me the changes are in).
You can also look at what would be required for wicket 1.5-SNAPSHOT
compatibility. Basically you would merge your changes from the 1.4
branch and then add the tinymce-parent entry back in the
jdk-1.5-parent/pom.xml file. That way when we start cutting 1.5
wicketstuff-core releases it will be included automatically.
Regards,
Mike
whats your sf.net username? i can give you access to svn.
as far as builds, Michael O'Cleirigh takes care of those on regular
basis. you might want to talk to him if you want more details.
-igor
On Fri, Oct 29, 2010 at 10:05 AM, Josh Glassman<josh...@gmail.com> wrote:
I would be willing to do so, at least temporarily. How do I get
commit permissions, and how do I get a build created and installed to
the maven repo?
On Fri, Oct 29, 2010 at 11:44 AM, Igor Vaynberg<igor.vaynb...@gmail.com> wrote:
dont think anyone is maintaining the project. you are welcome to take it over.
-igor
On Fri, Oct 29, 2010 at 8:40 AM, Josh Glassman<josh...@gmail.com> wrote:
Hi All,
Who if anyone is in charge of the Wicket Stuff TinyMCE project?
I have been having some issues with it and noticed that the TinyMCE
files have not been updated since the initial 3.3 release. I tried
simply replacing the tiny_mce folder inside a copy of the
tinymce-1.4.12.jar with the latest from the website and my issues are
completely gone now. Is there any chance we could get an updated
release with the newer files?
Now another question is coming to mind, is there any sort of standard
defined for how often an included dependency like this should be
updated? On one hand it would be nice to always have the most
up-to-date files available through maven, but on the other hand that
could be very time and resource consuming depending on how often the
dependency is updated. Thoughts? Suggestions?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
