2:11 p.m.
Hi team!
I plan to start to contribute new features on hibernate-tools-plugin but
was looking at jira and couldnt find any issue related. Do you have any
features on mind that you would like to attack first?
regards!
--
Alejandro Montenegro del Pino.
Santiago - Chile
phone: (+56) 9-68358690
3:16 p.m.
Hey Alejandro!
Awesome! Glad to have you :)
The plugin issues are actually tracked in their own individual lists on
GitHub: https://github.com/forge/plugin-hibernate-tools
As far as where to begin, I think I have just the perfect thing for you!
One of the problems with the Hibernate Tools plugin today is that in order
to generate from a database, you must type the configuration options every
single time you run the plugin. I think it would be great if we could tie
this plugin into the Forge configuration system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level
specifically when requested - see: getScopedConfiguration(), but by default
it will access the project level configuration first, then fall back to the
user configuration if that cannot be found or does not have an entry. In
this case, using the default behavior should be the right behavior.
We may need to add a few features to the core library itself in order to do
things like access the configuration from default @Option values, but we
can talk about that later.
In that regard, maybe you could try using the plugin a few times, then use
that to try to streamline the interactions so that they requires less
repetitive work? Is that a good place to start?
What do you think?
~Lincoln
On Thu, Jan 12, 2012 at 2:11 PM, Alejandro Montenegro <aamonten(a)gmail.com>wrote:
Hi team!
I plan to start to contribute new features on hibernate-tools-plugin but
was looking at jira and couldnt find any issue related. Do you have any
features on mind that you would like to attack first?
regards!
--
Alejandro Montenegro del Pino.
Santiago - Chile
phone: (+56) 9-68358690
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
3:17 p.m.
I also recommend that you fork the core repository and take a look at the
sources there so that you have an idea of what things look like :)
https://github.com/forge/core
~Lincoln
On Thu, Jan 12, 2012 at 3:16 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Hey Alejandro!
Awesome! Glad to have you :)
The plugin issues are actually tracked in their own individual lists on
GitHub: https://github.com/forge/plugin-hibernate-tools
As far as where to begin, I think I have just the perfect thing for you!
One of the problems with the Hibernate Tools plugin today is that in order
to generate from a database, you must type the configuration options every
single time you run the plugin. I think it would be great if we could tie
this plugin into the Forge configuration system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level
specifically when requested - see: getScopedConfiguration(), but by default
it will access the project level configuration first, then fall back to the
user configuration if that cannot be found or does not have an entry. In
this case, using the default behavior should be the right behavior.
We may need to add a few features to the core library itself in order to
do things like access the configuration from default @Option values, but we
can talk about that later.
In that regard, maybe you could try using the plugin a few times, then use
that to try to streamline the interactions so that they requires less
repetitive work? Is that a good place to start?
What do you think?
~Lincoln
On Thu, Jan 12, 2012 at 2:11 PM, Alejandro Montenegro <aamonten(a)gmail.com>wrote:
> Hi team!
>
> I plan to start to contribute new features on hibernate-tools-plugin but
> was looking at jira and couldnt find any issue related. Do you have any
> features on mind that you would like to attack first?
>
> regards!
> --
> Alejandro Montenegro del Pino.
> Santiago - Chile
> phone: (+56) 9-68358690
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
8:03 a.m.
Alejandro - and if you got questions/concerns i'm hanging out on #jbosstools and
sometimes #forge irc and can answer there too (or here via mail)
/max
On Jan 12, 2012, at 21:16, Lincoln Baxter, III wrote:
Hey Alejandro!
Awesome! Glad to have you :)
The plugin issues are actually tracked in their own individual lists on GitHub:
https://github.com/forge/plugin-hibernate-tools
As far as where to begin, I think I have just the perfect thing for you! One of the
problems with the Hibernate Tools plugin today is that in order to generate from a
database, you must type the configuration options every single time you run the plugin. I
think it would be great if we could tie this plugin into the Forge configuration
system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level specifically when
requested - see: getScopedConfiguration(), but by default it will access the project level
configuration first, then fall back to the user configuration if that cannot be found or
does not have an entry. In this case, using the default behavior should be the right
behavior.
We may need to add a few features to the core library itself in order to do things like
access the configuration from default @Option values, but we can talk about that later.
In that regard, maybe you could try using the plugin a few times, then use that to try to
streamline the interactions so that they requires less repetitive work? Is that a good
place to start?
What do you think?
~Lincoln
On Thu, Jan 12, 2012 at 2:11 PM, Alejandro Montenegro <aamonten(a)gmail.com> wrote:
Hi team!
I plan to start to contribute new features on hibernate-tools-plugin but was looking at
jira and couldnt find any issue related. Do you have any features on mind that you would
like to attack first?
regards!
--
Alejandro Montenegro del Pino.
Santiago - Chile
phone: (+56) 9-68358690
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
/max
http://about.me/maxandersen
9:51 a.m.
Sounds great, I will give it a try and reach you if I have any concern.
My nick at jboss/github/freenode is aamonten
thanks!
On Thu, Jan 12, 2012 at 5:16 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Hey Alejandro!
Awesome! Glad to have you :)
The plugin issues are actually tracked in their own individual lists on
GitHub: https://github.com/forge/plugin-hibernate-tools
As far as where to begin, I think I have just the perfect thing for you!
One of the problems with the Hibernate Tools plugin today is that in order
to generate from a database, you must type the configuration options every
single time you run the plugin. I think it would be great if we could tie
this plugin into the Forge configuration system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level
specifically when requested - see: getScopedConfiguration(), but by default
it will access the project level configuration first, then fall back to the
user configuration if that cannot be found or does not have an entry. In
this case, using the default behavior should be the right behavior.
We may need to add a few features to the core library itself in order to
do things like access the configuration from default @Option values, but we
can talk about that later.
In that regard, maybe you could try using the plugin a few times, then use
that to try to streamline the interactions so that they requires less
repetitive work? Is that a good place to start?
What do you think?
~Lincoln
On Thu, Jan 12, 2012 at 2:11 PM, Alejandro Montenegro <aamonten(a)gmail.com>wrote:
> Hi team!
>
> I plan to start to contribute new features on hibernate-tools-plugin but
> was looking at jira and couldnt find any issue related. Do you have any
> features on mind that you would like to attack first?
>
> regards!
> --
> Alejandro Montenegro del Pino.
> Santiago - Chile
> phone: (+56) 9-68358690
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Alejandro Montenegro del Pino.
Santiago - Chile
phone: (+56) 9-68358690
9:51 a.m.
Thanks Max!
On Fri, Jan 13, 2012 at 10:03 AM, Max Rydahl Andersen <
max.andersen(a)redhat.com> wrote:
Alejandro - and if you got questions/concerns i'm hanging out on
#jbosstools and sometimes #forge irc and can answer there too (or here via
mail)
/max
On Jan 12, 2012, at 21:16, Lincoln Baxter, III wrote:
> Hey Alejandro!
>
> Awesome! Glad to have you :)
>
> The plugin issues are actually tracked in their own individual lists on
GitHub: https://github.com/forge/plugin-hibernate-tools
>
> As far as where to begin, I think I have just the perfect thing for you!
One of the problems with the Hibernate Tools plugin today is that in order
to generate from a database, you must type the configuration options every
single time you run the plugin. I think it would be great if we could tie
this plugin into the Forge configuration system/API.
>
> // org.jboss.forge.env.Configuration;
> @Inject Configuration config;
>
> The configuration API can save and load data at the project/user level
specifically when requested - see: getScopedConfiguration(), but by default
it will access the project level configuration first, then fall back to the
user configuration if that cannot be found or does not have an entry. In
this case, using the default behavior should be the right behavior.
>
> We may need to add a few features to the core library itself in order to
do things like access the configuration from default @Option values, but we
can talk about that later.
>
> In that regard, maybe you could try using the plugin a few times, then
use that to try to streamline the interactions so that they requires less
repetitive work? Is that a good place to start?
>
> What do you think?
> ~Lincoln
>
> On Thu, Jan 12, 2012 at 2:11 PM, Alejandro Montenegro <
aamonten(a)gmail.com> wrote:
> Hi team!
>
> I plan to start to contribute new features on hibernate-tools-plugin but
was looking at jira and couldnt find any issue related. Do you have any
features on mind that you would like to attack first?
>
> regards!
> --
> Alejandro Montenegro del Pino.
> Santiago - Chile
> phone: (+56) 9-68358690
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
/max
http://about.me/maxandersen
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Alejandro Montenegro del Pino.
Santiago - Chile
phone: (+56) 9-68358690
4493
days inactive
4494
days old
5 comments
3 participants
participants (3)
-
Alejandro Montenegro -
Lincoln Baxter, III -
Max Rydahl Andersen